If I was to create my Catalog with the databases and tables for my application says for example:

Database = TestApp
Tables = Customer
   and CustomerDiscounts

I then install the application at my clients site and he creates more tables
within that catalog so he now has:

Database = TestApp
Tables = Customer
   and CustomerDiscounts
   and CustomerQuotes

What happens if I then decide that I need a new table for my application e.g. sites
So my catalog now has

Database = TestApp
Tables = Customer
   and CustomerDiscounts
   and Sites

How can I send this site table to my client so that it gets included in
his catalog without overwriting his "CustomerQuotes" table?

Chris Holland

Chris,

<< How can I send this site table to my client so that it gets included
inhis catalog without overwriting his "CustomerQuotes" table? >>

It will have to be created using a CREATE TABLE statement, and then the
actual table data be added via an import file or some other external method.
The table files keep the table structure version number in them, so it must
match the table structure version number in the catalog or else you'll get
an error.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


I'm glad Chris made his post cos I had that and another one.

Unless I'm misinterpreting this it means that unless the table you want to import is structure version number 1 you can't simply copy the necessary files in which basically means if you want to add a table with data to an already existing app (unless its structure version number is 1) you have to write the file out to a csv (for example) file, distribute that and then import it at the other end.

Is that what you're saying or am I putting words in your mouth?

Roy Lambert

Or you could Alter the table structure changing the version number
to 1.01 and then copy the new table into the directory?

Chris Holland

Roy Lambert wrote:
> Tim
>
>
> I'm glad Chris made his post cos I had that and another one.
>
> Unless I'm misinterpreting this it means that unless the table you want to import is structure version number 1 you can't simply copy the necessary files in which basically means if you want to add a table with data to an already existing app (unless its structure version number is 1) you have to write the file out to a csv (for example) file, distribute that and then import it at the other end.
>
> Is that what you're saying or am I putting words in your mouth?
>
> Roy Lambert
>

Chris


Just looked and reverse engineering does give you the version number. Well thought of. I should have checked but for some reason I thought it was a bit you couldn't alter.

Roy Lambert

Chris


One thing I just thought of, no matter how much I complain at least I know we'll get decent manuals unlike another component set I just bought where its trial, error and squint at the provided examples

Roy Lambert

Thats true, although there are a few blank spaces at the moment.

I was just having a browse trying to find out what
"Request Sensitive Result Set" meant in the SQL tab but had no joy.



Chris Holland



Roy Lambert wrote:
> Chris
>
>
> One thing I just thought of, no matter how much I complain at least I know we'll get decent manuals unlike another component set I just bought where its trial, error and squint at the provided examples
>
> Roy Lambert
>

Chris


Its the same as the DBISAM "Live Result Set" but in SQL standard speak. I knew I'd need to learn a new language for ElevateDB but expected it to be just for programming

Roy Lambert

Okay,

Thanks Roy

Chris Holland


Roy Lambert wrote:
> Chris
>
>
> Its the same as the DBISAM "Live Result Set" but in SQL standard speak. I knew I'd need to learn a new language for ElevateDB but expected it to be just for programming
>
> Roy Lambert
>

Roy,

<< Unless I'm misinterpreting this it means that unless the table you want
to import is structure version number 1 you can't simply copy the necessary
files in which basically means if you want to add a table with data to an
already existing app (unless its structure version number is 1) you have to
write the file out to a csv (for example) file, distribute that and then
import it at the other end.

Is that what you're saying or am I putting words in your mouth? >>

That's exactly what I'm saying.  If EDB has incremented the internal version
number used to track structure changes, then that means that the table
structure is no longer compatible with the new table that you're trying to
overwrite it with.  Therefore, if you *do* overwrite the existing table,
you'll totally screw up the table because the table contents won't match the
catalog anymore.  Of course, EDB prevents this by issuing an error when you
try to open it.

--
Tim Young
Elevate Software
www.elevatesoft.com