• WSsdepriest

    WSsdepriest

    @wssdepriest

    Viewing 15 replies - 1 through 15 (of 155 total)
    Author
    Replies
    • in reply to: Using a variable for a field name (A2K) #1011417

      Okay, that’s what I figured.

      I’ll see if I can generate an SQL string. Thanks.

    • in reply to: Using a variable for a field name (A2K) #1011396

      How about in a query?

      I’m storing the name of a field in a hidden text box on a form. I want to pass the name of that field to a query. Then that field in the query has criteria. So I want the query to select the field name dynamically based on what is in the hidden text box on the form.

      I’ve tried adding this to the field line in a query: [Forms]![Startup]![txtSectionFieldName] but the query returns no results. How do I do this?

    • in reply to: Append X number new records via VBA (2003 SP1) #1003456

      The values for Field2 would NOT be stored in a table. I would like to generate them some how, like start Value + 1 up to end value.

      Would I still use the For…Next loop for Field2?

    • in reply to: Mass Conversion Utility? (2003 SP1) #982865

      Thanks for the links to Wendell’s comments.

      I’m sure he knows what he’s talking about. I’m the Access support person in our company and so I’m wondering if we should stop our conversion efforts based on Wendell’s comments. I suppose I’ll have to check the other Access forums out and see if there are further complaints about the updated file format. I have noticed that after conversion to 2k3 that the file size is slightly larger than the same db in 2k format. So you and Wendell think that this increase in bloat causes a stability & corruption problem?

    • in reply to: Mass Conversion Utility? (2003 SP1) #982854

      Most of our DB’s are in the Access 2000 format, but by powers greater than me, it has been deemed to convert them all to the newest file format. (We upgraded from Office 2k to Office 2k3 this spring.)

      I’m aware of the fact that Access 2000 users won’t be able to open the Access 2k3 files and so are my managers. But our company is all using Access 2003, and since we have the ability to “dumb” down the MDB files, they don’t see that as a reason not to convert.

      Why do you say that the Access 2k format is smaller and more stable? I haven’t heard that claim before.

      I’ll check out that KB article in the meantime.

    • in reply to: run dos commands from Access? (2003 sp1) #974577

      That worked. Thanks.

    • in reply to: How to trap SQL Server errors in MDB? (2003 SP1) #970391

      Rory,
      Thanks, that worked. The message box does appear before the SQL server error. Thanks. Yes, it did return an error number of 3146, which is the ODBC call failed error.

      Just have to realize that the same message box will appear for other causes of the error 3146. So have to word the message box appropriately.

      Thanks again.

    • in reply to: How to trap SQL Server errors in MDB? (2003 SP1) #970386

      Correction!

      I removed the “On Error GoTo ODBCErrorHandler” part and the exit sub part as well. And now the error number was written to the debug window.

      But… It just returns the VBA Error of 0.

      So I don’t think that helps me any…

    • in reply to: How to trap SQL Server errors in MDB? (2003 SP1) #970385

      Yes, I tried that too. No luck. Doesn’t seem to get to that event before the SQL server error appears. This is the code I’ve used, modified for my situation.

      Private Sub Form_Error(DataErr As Integer, Response As Integer)
      On Error GoTo ODBCErrorHandler

      Exit_Sub:
      Exit Sub

      ODBCErrorHandler:
      Dim errX As DAO.Error

      If Errors.Count > 1 Then
      For Each errX In DAO.Errors
      Debug.Print “ODBC Error”
      Debug.Print errX.Number
      Debug.Print errX.Description
      Next errX
      Else
      Debug.Print “VBA Error”
      Debug.Print Err.Number
      Debug.Print Err.Description
      End If

      Resume Exit_Sub
      End Sub

    • in reply to: How to trap SQL Server errors in MDB? (2003 SP1) #970335

      It sounds like it will work.

      But I added the example Error Handler routine to the OnDirty, OnDelete, BeforeDelConfirm events of the form and the SQL server error appears before any of these events happen (or so it seems). Nothing appears in the Immediate Window. frown

      Any suggestions on where else I can put the error trap?

      Sarah

    • in reply to: Quick way to determine file format of mdb (2003 sp1) #966093

      Yeah, me either I guess. I thought there might be a hidden, right-click-on-the-mdb way or something, but must not be. Not a big deal.

      Thanks.

    • in reply to: Quick way to determine file format of mdb (2003 sp1) #966069

      I was aware of the Convert Database submenu as well, and thanks for the suggestion for the automatic way.

      But that is not built into all databases at the moment.

      My organization has chosen to convert all MDB’S to the newest file format, Access 2002-2003. So I have instructions for the users on how to do that, but I was looking for a way for them to tell what version the MDB is currently on. So unless there is another way, I’ll just instruct them to check the title bar, or maybe the Convert database sub menu, which ever turns out to be less steps for the users.

      Thanks.

    • in reply to: Way to force reminders on top of other apps? (2003 SP1) #965304

      You must have Windows XP.

      My organization is still on Windows 2000, and so we don’t have that group feature in the task bar. When I have a reminder, it always pops on top, no matter what app has the focus. The taskbar flashes, even if I have the task bar on auto-hide it will pop up and flash.

      Maybe I’ll have her run the /cleanreminders switch to see if that fixes anything.

    • Thanks for responding, jscher2000.

      No we don’t have roaming profiles in my organization. As for a PST file, the user’s OUtlook profile is attached to her Exchange mailbox, not a PST. I did create a profile based on a new, Outlook 2k3 PST file, but that didn’t cause Outlook Today to look funny. Maybe I’ll have the user try it herself, since Outlook Today is messed up on hers.

      Maybe she has an old 2000-PST in her folder list that could be causing something funny. I’ll contact her and find out.

      In the mean time, has anyone else seen this or can recreate it? Thanks.

    • in reply to: Form Reference for Criteria in a Crosstab (2003 SP1) #961351

      Oh you are so smart.

      That worked. Forgot about that. I take it that’s necessary with crosstabs. I know it isn’t for regular select queries.

      Thanks for the help.

    Viewing 15 replies - 1 through 15 (of 155 total)