If you split your database into front end and back end, you will only need to
update the front end "interface" access file instead of each individual object
within the database.
-------------- Original message --------------
From: mick_curtis <[EMAIL PROTECTED]>
I had a cool idea about how to improve Access...
This concerns making a test system's changes become part of the Live
system.
My current habits are as follows:
In my test system, I make structural changes to tables, forms,
queries, reports, etc. and I need to note manually exactly what it
is that I am changing. I can use the 'Date Modified' Details of
queries to see what was changed recently, then, upon going live, I
have to manually rename or remove old queries so that they are
overwritten by my new queries. Similarly, I can replace reports,
tables structure (NOT the Live DATA!).
I am sure that an automated process could compare my test system and
a designated Live system and a wizard could start up to ask me if I
want to do a change to a table structure, a query, a report, etc. It
would reduce the chance of me missing a step when I try to go from
Test to Live. It could also write the documentation with less risk
of a documentation step being misseed out.
Does anyone else have a wish list of Access extra functionality?
Mike
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AccessVBACentral/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
