Tim

This one drove me round the bend for hours. In fact I was beginning to think you were being paid to drive me mad.

Creating a new database creates the config and catalogue files but doesn't create the tables unless you open them. Is that right?

Roy Lambert

Roy,

<< Creating a new database creates the config and catalogue files but
doesn't create the tables unless you open them. Is that right? >>

Yes.  Remember, catalog information is separate from the tables and the
existence of the table files themselves are irrelevant to whether the table
is considered to exist.  The catalog information determines the existence of
a table or tables.  If the table files don't exist, then EDB creates them as
necessary.  Otherwise you'd have a case where you'd see the table listed in
the EDB Manager and an attempt to open it would cause a "table not found"
error.  Not very good.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< Creating a new database creates the config and catalogue files but
>doesn't create the tables unless you open them. Is that right? >>
>
>Yes. Remember, catalog information is separate from the tables and the
>existence of the table files themselves are irrelevant to whether the table
>is considered to exist. The catalog information determines the existence of
>a table or tables. If the table files don't exist, then EDB creates them as
>necessary. Otherwise you'd have a case where you'd see the table listed in
>the EDB Manager and an attempt to open it would cause a "table not found"
>error. Not very good.

Now I know it I'm happy - just make sure you document it in BIG LETTERS in the manual. I've spent literally 3 hours going round with this one (and yes I know its a DBISAM/BDE heritage). Copied the code from your example and nearly went berserk with it. Used Windows Find looking for the tables and finally thought I'll hook one up to a DBGrid and see if its been created somewhere I know nothing about and Eureka.

Roy Lambert