I don't know if I'm seeing problems where they don't exist, or just getting paranoid or wether there is genuine cause for concern.

This arose from the small app I wrote as part of learning ElevateDB (a low feature cash book for my domestic use). Playing with user defined functions I made an alteration in the catalog, in 1.07b3 whilst the app was last compiled with 1.06. Naturally when I went to run the app I received an error.

#100 error in the metadata for the catalog.

A quick recompile and everything was fine, but it started me thinking.

Picture this scenario

Someone using an older version of an app of mine has a problem, sends me the tables and catalog, I find the problem and fix it. As part of the process I do things to the catalog/data in EDBManager. I ship the fixed data back. The user now gets error #100.

They're not prepared to pay for a newer version of the app, I'm not prepared to supply one for free since I've done a lot of work on new features.

Is this paranoid or probable?

Roy Lambert

Roy,

<< Someone using an older version of an app of mine has a problem, sends me
the tables and catalog, I find the problem and fix it. As part of the
process I do things to the catalog/data in EDBManager. I ship the fixed data
back. The user now gets error #100.

They're not prepared to pay for a newer version of the app, I'm not
prepared to supply one for free since I've done a lot of work on new
features.

Is this paranoid or probable? >>

It's probable if you're not careful.   The lesson is to not use newer
versions of EDB on databases that you intend to send back to customers that
are using older versions of EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:6B049FEC-23E2-4BBE-B3A0-AF0AC3037FC3@news.elevatesoft.com...
>I don't know if I'm seeing problems where they don't exist, or just getting
>paranoid or wether there is genuine cause for concern.

Trouble is new stuff Roy your not paranoid new stuff never works how you
would like it too.
When I go the EDB root you woild have answered all my questions and got
Tim to add goodies keep it up

My latest venture is a site with all the Ebay category's 327 subfolders
under
Antiques alone they were going in an IWTreeView now a dbcombo.
Someone who I will not name said go Firebird I said no coz DBisam will
handle it.

Tim


>It's probable if you're not careful. The lesson is to not use newer
>versions of EDB on databases that you intend to send back to customers that
>are using older versions of EDB.

Its a wonderful answer but somewhat impractical since it means keeping a version of EDBManager (at least) for every version someone out there has.

Roy Lambert

Roy,

<< Its a wonderful answer but somewhat impractical since it means keeping a
version of EDBManager (at least) for every version someone out there has. >>

It's either that or not have the ability to add in new features to the EDB
catalog in minor releases, thus also requiring a format change for any major
releases like DBISAM had.

However, keep in mind that this only applies to structural changes to the
database catalog.  When you say that you're "fixing" databases, are you
running DDL statements against them or just modifying the row data ?  If
you're just modifying row data, then doing so with the latest EDB Manager
won't have any effect upon the database catalog version at all.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

><< Its a wonderful answer but somewhat impractical since it means keeping a
>version of EDBManager (at least) for every version someone out there has. >>
>
>It's either that or not have the ability to add in new features to the EDB
>catalog in minor releases, thus also requiring a format change for any major
>releases like DBISAM had.
>
>However, keep in mind that this only applies to structural changes to the
>database catalog. When you say that you're "fixing" databases, are you
>running DDL statements against them or just modifying the row data ? If
>you're just modifying row data, then doing so with the latest EDB Manager
>won't have any effect upon the database catalog version at all.

At this point who knows what I'll be doing - that's the beauty of customers

I can sort of feel the horror emanating from you with this next suggestion - How about a utility to "turn back" the version number in both catalog and tables?

Roy Lambert

Roy,

<< I can sort of feel the horror emanating from you with this next
suggestion - How about a utility to "turn back" the version number in both
catalog and tables? >>

I'll have to see if that would be justified in terms of the time it would
take to do vs. the number of times this sort of thing will come up.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>I'll have to see if that would be justified in terms of the time it would
>take to do vs. the number of times this sort of thing will come up.

I was expecting to see smoke coming out of your ears

Roy Lambert