Robert L. Stewart
rl_stewart at highstream.net
Wed Mar 3 09:34:46 CST 2004
Sander, Like I said earlier, you are going to have to write the code to do this. And, each time there is a change, you will have to add the change code also. You might be able to use the BEU that someone else suggested. But I do not have any experience with it, so I cannot tell you how to do it. The problem will be getting the delta (changes) between the current version and the development version automatically. In the development area, you will have to freeze teh code, and extract the differences between the current production and the frozen copy. By freezing the development copy, you can continue making changes for the next release without affecting your "ready for production" copy of the development db. Sorry, but it is too big a project just to write the code for you and post to the list. It would probably take a couple of weeks to write and test it. And that would be working on it full time. Robert At 08:09 AM 3/3/2004 -0600, you wrote: >From: S D <accessd667 at yahoo.com> >Subject: RE: [AccessD] Re: Create scripts: CreateTable? >To: Access Developers discussion and problem solving > <accessd at databaseadvisors.com> >Message-ID: <20040303131340.30199.qmail at web61104.mail.yahoo.com> >Content-Type: text/plain; charset=us-ascii > >thnx for the replies. > >History: >I work for company A and I'm stationed at Customer B. I'm hired by >Customer B to develop stuff. Customer B has also hired company C to >implement/migrate changes. Company C has a rule that they ONLY use scripts >to implement/migrate changes that can be run by 'ZERO-KNOWLEDGE-USERS'!! > >That is why I need a piece of code to generate CreateTable scripts. I need >this piece of code in Access 2000. > >if anybody neesd any more info don't hesitate to ask. > >Regards, > >Sander