Why on Earth would you WANT to?
This would be storing the value redundantly. If it can be looked up from the
Wells table, do so! Storing the field redundantly in a second table is just
asking for trouble, since it could in principle get edited in either or both
locations; you would then have two different values for Lon with no way to
tell which one is right.
Context please?
--
John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see alsohttp://
www.utteraccess.com
John:
Why on Earth would you WANT to?
ommmmm,...............
your point is very well taken, and for most parts I agree with you.
but my reality limits my options due to not having the authority in my
job to tell people above me what they should have. You need to
realize that I just dig the hole. for some peculiar reason they want
to have it recorded with the case. I thought abt the point you made
earlier of it having the chance of being different that what the look-
up table has. My approach was to make the fields in the form read
only so the user can't edit, this way what DLookup reads is what they
record. is there a chance of the Look-up table getting updated with
new lon/lat for each point. very rare or near to none. due to the
fact that most of the points have been GPSed. now if it dose than I
need to make some correction on the back-end. The table is not
reachable from user manipulation all actions are done through forms
and the menus have been disabled. It is probably not the best
approach, but this is the best I can do with limited time and
knowledge I have.
I still do appreciate your thoughts(it keeps me out of trouble) and am
thankful to this community, I have always gotten good feedback from
this community.
Regards
Ardy