William Hindman
wdhindman at dejpolsystems.com
Fri Aug 18 12:24:29 CDT 2006
...for those of us without such a tool ...or for those of us who prefer doing it with Access when we can, this appears to be a code set that can be customized to suit our individual needs and modified as need be ...its certainly not going to replace professional third party tools in every instance nor is it so intended. ...as for the export/import I don't track that ...I routinely do that to app versions I'm preparing for release to a client ...it may be overkill but it only takes one bad release to justify the extra step in my routine ...this simply provides code to automate that process along with a number of others that can be added. William ----- Original Message ----- From: "Charlotte Foust" <cfoust at infostatsystems.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Friday, August 18, 2006 11:56 AM Subject: Re: [AccessD] ...a new tool? > We already have a tool that works for us. However, we aren't trying to > automate the things he seems to feel are important. We simply compact > out a copy of our database and run it through a process to set its > security, remove any linked tables, scrub and sanitize the thing, and > get it ready to go out the door, including decompiling and recompiling > it, compacting it, etc. I see no point in importing stuff into another > database like that. > > Charlotte Foust > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters > Sent: Friday, August 18, 2006 8:46 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] ...a new tool? > > If you have a number of extra steps that he couldn't have foreseen, then > you're right - this isn't the tool for you. > > But, since you do have more steps, there is even more reason for you to > have an automated method to prepare a database for release (computers > are more reliable than people!). And, his source code is available, so > could you add capability to his code and have a tool that works well in > your environment? > > Dan Waters > > > -----Original Message----- > Subject: Re: [AccessD] ...a new tool? > > We run our apps through a process, but it operates against a database > that has already been compacted out of source safe and needs to have > security set, links removed, and certain data in the tables cleared or > set. I don't see much point in what he's doing. > > Charlotte Foust > > -----Original Message----- > Subject: Re: [AccessD] ...a new tool? > > This looks like a tool that would introduce a consistent mechanism for > preparing to release a database. Looks good - I'll try it. > > Dan Waters > > -----Original Message----- > Subject: [AccessD] ...a new tool? > > http://www.codeproject.com/vbscript/AccessBatchBuildAllFiles.asp > > ...anyone have a better idea on how to do this? > > William > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com