Pedro Janssen
pedro at plex.nl
Wed Apr 20 16:03:05 CDT 2005
Hello all, thanks for the help so far, but as Charlotte suggested, i will explain a why i need this. My wife works in a small firm that sells rocks. I developed in recent years a database for them, in which they can put data about the rocks and the clients who sell them. When the firm grew bigger, they invested in a commercial database for administration. In this database however, i can't change anything. Because my wife don't want to ad each new client in two different databases. So i want to use the client table from the commercial database, because the clientID's are identical. I don't want to use a query from this linked table, because i then have to adjust al other query's and other tables. Because the linked table is only used as a lookup table i want to use it, but the name of the table and the field names are different. Because the commercial database will give the users the possibility of using characters an numbers in the ID field, i want to change this datatype from text to number. I'll hope you'll understand why i asked for the possibility of making a copy of the linked database by code or autoexec macro, and change the name, field name and datatype of this copy? Pedro Janssen ----- Original Message ----- From: "Stuart McLachlan" <stuart at lexacorp.com.pg> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Wednesday, April 20, 2005 12:01 AM Subject: Re: [AccessD] changing table in linked backend > On 19 Apr 2005 at 23:20, Pedro Janssen wrote: > > > Hi, > > > > is it possible to make a copy of the linked database by code, and change the > > name, field name and datatype of this copy? > > > > One way would be to create a new table with the desired format either > directly in your application database or or in a separate "backend" > database and link to that as well as to the original table. Then > periodically run two queries , a delete query to clear your new table > followed by an Insert query of all the records from the old table into the > new table. > > If there is a unique key in the old table, you can set a unique index on > that field in the new table and forget about the delete query. > > Note that if you are doing this frequently, you will have to compact the > database regularly or you will get very bad bloat. > > > > > -- > Stuart > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >