You might get most of the references fixed in stored objects (but not code) if you have Name Autocorrect enabled. It's another thing that the experts say shouldn't be turned on but I don't have a link handy for that one.
You might get most of the references fixed in stored objects (but not code) if you have Name Autocorrect enabled. It's another thing that the experts say shouldn't be turned on but I don't have a link handy for that one.
This info helped a lot. I'm watching that YouTube series by "programming" that has made me rethink how to set up my tables better. That's has to be many of my issues.You haven't entered any criteria in the dlookup though?
I did though.
I see no criteria in this expression: PLocalTime = DLookup("MyTimeZone","Settings")
Without criteria, you get the field value from the first record in the table, so you are probably correct about the table design. I see no field that you can filter on, such as UserID, to get the time shift value according to the user.
I think many here would agree with the notion that you should dispense with lookup fields in tables. Here's why http://access.mvps.org/access/lookupfields.htm
Sent from my iPhone using Tapatalk
Then these might help as well:
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.ca/...on-part-i.html
and/or
http://holowczak.com/database-normalization/
One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp