Yeah, all the address fields, they're currently seperate
combo boxes
Address #
Practice Name
Address
City
State
Zip
These are fields from the tblAddress, linked by ADDR# to tblRepSiteVisit.
They enter by address number, so by entering the address number, the rest of the combo boxes should...
Nope, no luck, changed all the address fields and still not keeping them together or autopopulating. I've had problems with this database since I inherited it two months ago.
If I go with the combo box, will the rest of the address fields auto populate when the address number is entered from tbladdress, if I use the dlookup function?
would the dlookup function populate the other address fields afterupdate. Probably so, but would the six address fields need the dlookup in the afterupdate property as well?
Oh, do I need the query for this?
Ok, I've put this on the form, in the ADDR text box, using DLookup («expr», «domain», «criteria») as a guide.
Would it then look like this:
DLookup ( [tblAddresses]![ADDR#] , «criteria»)
Hey guru's. I've been working with this form (S Contact Sheet)now for about two days . It's based off of a query (qryRepSiteVisits) with two tables(tblaAddresses and tblRepSiteVisits)in the query.
The form will be a data entry type of form that will assign a 'visit' (auto)number for each...
There is a field for 'COMMENTS', whre they do just that, in the CONCERNS table. Is there a way I can limit them from entering another case/record for the same patient.
This is similar to a customer database, except that it is patient based. But since each new 'complaint' is different that the one before, and not very many are the same, It would require a new 'concern number'. Normally there is no duplication, but lately the RN's have been adding a second...
How difficult is it to merge two tables that are linked by a control number without mixing them up. I have two tables that make up a form and a sub form linked by a control number. I want to make one table out of them to eliminate duplicating "concern" information in the subform. This...
I'm working on a copy so, I haven't lost any data yet, I'm just trying to get it to work in 2000. I think I'll work on the macros in 97, then take it to 2000, see how that floats. Thanks.
It's still not working, still getting the same messges. I'm getting desperate. If we upgrade to 2000, I won't be able to get this working. Any other ideas? Unless I create the macros for ALL the commands then redirect, but I'm hoping to get around that somehow.
I'm also having a few issues with Access 97 going to 2000, I'm getting messages like "File not found" and "The Visual Basic for Applications project in the database is corrupt". Any ideas as to how I can get all my forms into 2000. Additional Note: the buttons on the 97...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.