You should split the application into a front-end and a back-end.
The front-end is the user interface: Queries, Forms, Reports, Macros,
Modules, and any local look-up Tables whose data does not change. It will be
linked to the Tables in the back-end. You can replace the front-end at will
without affecting the data. You will not have to replace the runtime support
when you replace the front-end database.
The back-end is the data store: tables, relationships, and data. Only if you
change the data structure do you need to change the back-end. That will be a
more complicated change, and it will be very specific to your data
structure.
Typically, a fully-developed application will not expose the Database Window
to the user, so they will not see queries -- only Forms and Reports that you
display to the user.
Modifying a back-end without interfering with existing data and developing
applications are subjects of a greater scope than can be handled in a simple
newsgroup post.
Some intermediate to advanced books that I think might be useful are _Access
<version> Developer's Handbook_ by Litwin, Getz, et al, published by Sybex
and _Programming MS Access <version> by Dr. Rick Dobson, published by
Microsoft Press. If those prove too advanced, try _Microsoft Access 2003
Inside Out_ by John Viescas, published by Microsoft Press and/or _Special
Edition Using Access <version>_ by Roger Jennings, published by Que.
You might also take a look at the Training links on
http://office.microsoft.com -- there are a number of online training
sessions, each brief enough to be convenient. The FAQ site at
http://www.mvps.org/access is full of good information and links. You'll
find more links, some different than the ones on the FAQ site at
http://ntaccess.tripod.com, in the Resources section.
Larry Linson
Microsoft Access MVP
"Brenda" <br****@mycolle geinfo.com> wrote in message
news:41******** **************@ news.newsgroups .ws...
Is it possible to Syncronize with a CD to Access Runtime? I have a
program that needs to be updated yearly and we are trying to find the
best way to distribute it and then update it without loosing the data
that is entered in the mean time. Some of the computers have Access and
some do not, so runtime must be included, but I am not sure how to
update querys and forms that can be distributed without loosing data.
I would also like to know how to make queries not visible so the
reciever is not able to see what queries are used.
Thank you for all of your help.
Brenda
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
