Erwin Craps - IT Helps
Erwin.Craps at ithelps.be
Fri Dec 12 10:56:57 CST 2003
Euh, Just replace the whole file as I do... But I conclude that your are not using the Front/Back End technique? You should put all your tables in one MDB (the backend) and all your other stuff (queries, forms, macro's, code, reports) in a seperate MDB (or MDE) (The Frontend) If you make changes to the front end you just give everyone the new file... At the level of the tables, those change less often, you have at least tree solutions. 1) Write them down. 2) On the database advisors website there's a tool that for automatic backend updater. 3) Use a tool like Access Detective from FMS to compare two MDB and change the changes manualy (is what I do). Erwin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: Friday, December 12, 2003 4:18 PM To: Access-D Email (E-mail); ACCESS-L Email (E-mail) Subject: [AccessD] Access 2002 - module modified dates all changing at once. x-posted to Access-D and Access-L Access 2002: I just noticed that if I make any change to any module in Access 2002 then *all* the other modules have their modified date changed as well as the one that really was changed. This is a major pain in the neck as now I have to keep a manual record of what modules I just changed in my development copy so I know what to export to the production copy. Is it just me???? ;-( Lambert _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com