Replacing design without affecting data

[Guest]

I have recently started creating standalone MS Access applications for a few
clients of mine.

I install the db at client location and keep a copy of the same with me in
my office. Now when client requests for a design change or upgradation, is
there a way for me to make the design change in my copy of the database and
send it to him such that he only refreshes the design of the database
installed at his location without affecting the data there.

At the moment, I have to make my monthly visits to each location to make
design changes. (i m sure there is a better way than that)

Also, say if i were to compile the MSA db into an exe file (havent tried it
so far - but have seen the option in help). Will i be able to refresh the
design later (again without affecting the existing data).

Please help.

Naazneen

 

[Rick Brandt]

I have recently started creating standalone MS Access applications
for a few clients of mine.

I install the db at client location and keep a copy of the same with
me in my office. Now when client requests for a design change or
upgradation, is there a way for me to make the design change in my
copy of the database and send it to him such that he only refreshes
the design of the database installed at his location without
affecting the data there.

At the moment, I have to make my monthly visits to each location to
make design changes. (i m sure there is a better way than that)

ALL distriuted Access apps should be split into two files. One for the data
tables and the other for everything else. Since most design changes do not
affect the data tables all you do to update the users app is replace the "front
end" file with a new one.

Also, say if i were to compile the MSA db into an exe file (havent
tried it so far - but have seen the option in help). Will i be able
to refresh the design later (again without affecting the existing
data).

Access apps cannot be compiled to an exe. What you have seen is the abilty to
create an MDE version of the file. An MDE is not an executable but merely a
copy of your file where design changes to code-based objects is no longer
possible. Use of an MDE would basically force you to go to a split design as
outlined above since you would not be able to change the user's file any longer
and would only be able to implement changes by replacing it.