• WSJimDettman

    WSJimDettman

    @wsjimdettman

    Viewing 15 replies - 16 through 30 (of 41 total)
    Author
    Replies
    • in reply to: Calculating Dates (Access 2000) #544335

      That should work fine as long as both are Date/Time fields, which their not. Check the data types your using.

      Jim.

    • in reply to: Very important question (Access2000) #544334

      If you unwilling/cannot change the design, then fixing up the data is the only solution. Write an update query to look for the extra character:

      =”SSB_BCP_”

      and update to:

      “SSB_BCP”

      Of course that does nothing for fixing the problem itself as it can easily happen again.

      Jim.

    • in reply to: Very important question (Access2000) #544327

      So if I understand correctly, your saying this is a input error?

      You should be validating the broker code at time of input rather then trying to fix the problem of a incorrect code later on.

      Jim.

    • in reply to: front end distribution to user desktop (97) #544326

      ODE – Office Developers Edition – You only need it if the folks your distributing to don’t already have a copy of Access installed.

      Jim.

    • in reply to: Limited Fields in Forms? (Access 2000) #1788714

      The limit for the number of fields in a table or query is 255. The limit for the number of controls on a form is 754.

      As Mark said, you need to rethink what your doing.

      Jim.

    • in reply to: front end distribution to user desktop (97) #544258

      It’s not clear from you question if your remote users already have Access installed or not. You only need the ODE if the users your distributing to don’t already have Access installed. Otherwise, they just need a copy of the MDB file and any supporting files.

      Jim.

    • First, you should update to SR2 anyway just because of bug fixes. But if you want to avoid that I think you can because you probably won’t need to run JETCOMP as long as the regular one works.

      Instead do this:

      1. Create a fresh MDB container and import everything into it. This will (in most cases) eliminate any database corruption.

      2. Before opening, delete any .LDB files in that database directory. Typically, when someone disconnects abnormally, you’ll end up with an entry in the .LDB file giving you a phantom user. Deleting it will clear this up.

      3. Check the client PC’s were this is happening. Ensure that the TEMP and TMP environment variables point to a valid drive/directory and it has plenty of free disk space. This addresses the “out of memory” error, which may be the main cause of your problem.

      4. If the MDB is on a Novell Server, you may need to adjust the locks up or use the dbEngines SetOption method to set the max locks that JET can use below the setting in Novell. “Out of memory” occurs for a number of reasons other then being out of memory. This is one of them.

      HTH,
      Jim.

    • in reply to: Use Outlook as data store for Access? (Office 2000) #535475

      There are quite a few MSKB articles on pulling data into Access from Outlook as well as updating Outlook data from Access.

      Go to MSFT’s web site and do a search in the KB for product Access and keyword Outlook.

      Jim.

    • Just an FYI. The substitution argument is optional unless used in a query, so Mark’s code would have worked.

      Jim.

    • For subforms with no records, you need to use something other then NZ() (Null to Zero). That’s because a subform/subreport with no records returns an error. So there are two ways to handle it:

      =IIF(IsError(NZ( Me!ControlA,0) + NZ( Me!ControlB,0) ,0,NZ( Me!ControlA,0) + NZ( Me!ControlB,0) )

      or the method I perfer:

      =AvoidError(Me!ControlA + Me!ControlB)

      AvoidError being the following function that you paste into a module:

      Function AvoidError(n As Variant)

      On Error GoTo Trap
      AvoidError = n
      Exit Function

      Trap:
      AvoidError = 0
      Resume Next
      End Function

      Note that you can modify AvoidError to check for Null as well if you wish and return a 0.

      Jim.

    • in reply to: Access Reports (A97 SR2) #1786518

      Oh no….the really tough sell.

      Jim.

    • in reply to: Access Reports (A97 SR2) #1786507

      Fairly difficult. I can think of two ways to do it, neither very attractive and I probably can come up with a few more.

      Try and talk the client out of it. You’d be doing them a favor. The report will waste paper (ie. Nurse1 has more patients that 2 or 3 leaving lots of white space) and be more difficult to read. Also, if additional info is required in the future, it would be difficult to modify the format.

      They really need to avoid taking the “spreadsheet” approach to report design. The two don’t mix.

      Jim.

    • in reply to: Access Reports (A97 SR2) #1786505

      Yes it’s doable, but a very difficult report to format and one that’s not very flexable as the the horizontal space limits the number of nurses that can appear on the report.

      You’d need to fill in a few more details before I would suggest a method for doing this. For example, is this a horizontal snaking format? i.e.

      Nurse1 Nurse2 Nurse3
      Patient Patient Patient
      Patient Patient Patient

      Nurse4 Nurse5 Nurse6
      Patient Patient Patient
      Patient Patient Patient

      Nurse7 Nurse8 Nurse9
      Patient Patient Patient
      Patient Patient Patient

      But the real question is, why would you want to. Your fighting natural report design all the way. If you outline what your trying to accomplish, there my be a better approach that someone could suggest.

      Jim.

    • in reply to: cannot advance using nextRecord in report (97) #535293

      The correct way is:

      NextRecord = True
      PrintSection = False
      MoveLayout = False

      Jim.

    • in reply to: Calculated fields in a table (Access 97) #535292

      Bob,

      I would not put a duplicate check on the name, but instead on the phone number.

      If that is not workable, then you’ll need to add more info to the student table to prevent duplicates or you may find that you cannot prevent them and will need the human touch to keep them from happening (ie. display a list of sudents when a name is keyed in and allow the user to pick one). It really all boils down to how do you really identify a student?

      Jim.

    Viewing 15 replies - 16 through 30 (of 41 total)