Search results

I do not like forms that open with a dialog asking for information. A misspelling can have you looking at a blank form. Allow the user to make a selection from a combo box or list box instead and open the form based on their selection. No possible errors using this method... That is my 2 cents...

I am glad the code did the trick for you... Jack

Code similar to this in a Multi-Select list box should do what you want: Dim varItem As Variant Dim strWhere As String For Each varItem In Me![InvList].ItemsSelected strWhere = strWhere & "UPC# =" _ & Chr(39) & Me![InvList].Column(0, varItem) & Chr(39) & " Or " Next varItem strWhere =...

10,000 is not very many records for Access so why not try the DCount() and see what happens as you can always use code if it proves too slow... Take a look at this article as it should help you solve the problem of the 'Too few parameters...' error. hth, Jack

If DCount("[ClientNum]", "TrustPinNumbers", "[ClientNum] = " & Me.txtClientNum) >= 2 Then MsgBox "More than one Record with this client number" End If If you have bazillions of records then this will not be the fastest route, but it should do the trick. hth, Jack

I don't have 2003 but try this syntax: DoCmd.OpenForm "frmLCO", acNormal, , _ "[LCONum] = " & Forms!frmLCOViewingForm!subfrmLCOView.Form.LCONum hth, Jack

Pat - I have your db and will be looking at it shortly. The reason for this post is to let you know that your email box at Hotmail is full and I cannot send you an email... Jack

Hmmm. Am I correct in assuming that the Upper and Lower limits for each type of test are constant? If that is so then why not just have the Upper and Lower limits as labels on the form? You can use code in each text boxes Before Update event to verify that the value entered is between the Upper...

Hiya Pat!!! I wasn't sure if that was you or not, but now I am sure that it IS you! I surely do remember helping you in the past with a database that ended up with 12 million tables, forms and other bits of flotsam....or there about... I hope this finds you well and I can see that your are...

If you have done everything possible and the forms and reports will not work then you are, as far as I know, out of luck. If you have a backup then that is your salvation otherwise it is back to creating new forms and reports... As to why this happened I haven't a clue. Sometimes things go awry...

The subform should only be bound to the tblAlphaList. Adding data in the Mainform should not add records in the subform unless you have code to append data to the subforms table. An example is Customers and Orders. The Orders table is joined to the Customer table through CustomerID and linked...

Try importing everything into a new, blank db. If that does not fix the problem then import everything except the forms/reports that are not working. Then import them one at a time and test the db after each import. If you still have corrupt forms you are probably looking at using your backup or...

NachoMan - I am glad you have your problem solved.... Jack

NachoMan - I would only use one table but I would not have the log book number part of the TRNumber. The table would look like this: tblMyLogBookTable MyTableID (PK and autonumber) LogBookID (FK) TRNumber ...other fields... tblLogBooks LogBookID (PK and autonumber) LogBookName Now when the...

You're welcome! Jack

The reason that I do not use that approach is that Access pops up an error message that can be confusing to a user. If I can catch the error then I can put up a message that can be much more explicit and, hopefully, helpful. And I have more control over what happens after the 'error' occurs...

I am not sure where you are triggering the code, but this should work... LastAdded.Caption = DMax("[AccountN]", "TableNameHere") hth, Jack

Create forms based on the queries then list the forms instead of the queries themselves. That should do what you want... hth, Jack

As long as you don't have a bazillion records then this should do the trick (DLookup() is slow if there are a bazillion records): If Not IsNull(DLookup("LastName", "tblCustomers", "[LastName] = '" & Me.[LastName] & "'")) Then MsgBox "You have entered a duplicate value." Cancel = True...

I would put code in the Before Update event of the control to see that the input is not a duplicate. If it is then cancel the update and let the user try again. hth, Jack