I have some "resource tables" my apps use which are separate from the core data of the customers  database (effectively they are my own DBISAM versions of some parts of EDB Information.Tables tables).

For example a "ResourceStrings" database which holds ... you guessed it ... Resource Strings!

When I create a new DBISAM app I just cut & paste the DAT / IDX files for these tables into a new folder & make this the starting point for a new app.

What is the more elegant EDB way of doing this type of thing?

I can see if I just paste files into a folder the tables won't be in the catalog. I can hack the catalog files (Ugh), but I would rather COPY or MOVE the tables across.

Adam,

> I can see if I just paste files into a folder the tables won't be in the catalog. I can hack the catalog files (Ugh), but I would rather COPY or MOVE the tables across.

There is an easy way using EDBManager.

1. Create a new Script
2. Drag the table you want to copy between BEGIN and END of the new
empty Script.
3. Answer the question "Would you also like to include the SQL for
inserting existing rows ?" with YES.

Now you have a complete script that you can save and/or execute in your
new database.

Regards Uli

Adam


Method 1
First you have to migrate the tables (database) into ElevateDB.

Then in ElevateDB reverse engineer including rows, open the target database and execute the script.

Method 2
Copy the config, catalog and appropriate tables files into the new directory(s)
Open EDBManager and create a new session pointing at the config file
Open the session, select the database and edit the database to point at the new directory
Open the database drop the tables you don't want

Another thought is that is these tables AND their contents are common to your apps park then in a different directory and just reference them as another database within your apps.

Roy Lambert [Team Elevate]

Thanks guys this is really helpful.

I am _really_ enjoying the conversion process ... which I had rather dreaded (which is why I put it off so long!) Just converted my first app in about 4 hours (including all changes to Delphi code + all EDB SQL changes!)

Adam,

<< I am _really_ enjoying the conversion process ... which I had rather
dreaded (which is why I put it off so long!) Just converted my first app in
about 4 hours (including all changes to Delphi code + all EDB SQL changes!)
>>

See, Roy !  It can be enjoyable....

Nice job, Adam.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< I am _really_ enjoying the conversion process ... which I had rather
>dreaded (which is why I put it off so long!) Just converted my first app in
>about 4 hours (including all changes to Delphi code + all EDB SQL changes!)
> >>
>
>See, Roy ! It can be enjoyable....

I too found it enjoyable as soon as I found the right brick wall to bang my head against

Roy Lambert