I decided to delay getting drunk for an hour or so whilst I tried to do the first pass of the app to ElevateDB.

I used my standard home brew utility to alter

TDBISAMTable to TEDBTable
TDBISAMQuery to TEDBQuery
TDBISAMSession to TEDBSession
TDBISAMDatabase to TEDBDatabase
TDBISAMEngine to TEDBEngine

Open the app in D2006, get the normal warnings about missing properties, but I also got a streamread error. This on the form with the engine, session and database components. So I exited without saving, hacked the dfm to remove all properties that I was given a warning about, saved it, and tried opening the app again. Opened that form OK but checking the main form - no table components. Datamodule with loads of lookup tables shows one only, some other forms have lost their tables and others have streamread errors.

Anyone else have these problems or have a suggestion. I seriously do not want to have to alter all tables and queries by hand.

Roy Lambert

Roy,

<< Open the app in D2006, get the normal warnings about missing properties,
but I also got a streamread error. This on the form with the engine, session
and database components. So I exited without saving, hacked the dfm to
remove all properties that I was given a warning about, saved it, and tried
opening the app again. Opened that form OK but checking the main form - no
table components. Datamodule with loads of lookup tables shows one only,
some other forms have lost their tables and others have streamread errors.
>>

Somewhere along the line you/Delphi IDE accidentally removed the table
components.  What you should do is simply load each form, and ignore any
warnings about errors in the properties.  Only if the form won't load one of
the components at all should you manually edit the .dfm to remove the
offending properties in order to allow the component to load.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Somewhere along the line you/Delphi IDE accidentally removed the table
>components. What you should do is simply load each form, and ignore any
>warnings about errors in the properties. Only if the form won't load one of
>the components at all should you manually edit the .dfm to remove the
>offending properties in order to allow the component to load.

I certainly didn't I'll see if the IDE will play nicely tonight.

Roy Lambert

Tim


Makes no sense at all, but I couldn't get on with trying to earn money with this nagging at me so I experimented.

If I remove

   EngineVersion = '4.25 Build 5'

from all the dfm's its fine - well no more than the standard problems I expect with an alteration of this magnitude.

My datamodule contains an engine, database, session and a couple of tables. The other tables are on forms. Remove the offending line from the datamodule and it loads without the stream error, leave it in the forms and no tables show.

Roy Lambert

Roy,

<< If I remove

EngineVersion = '4.25 Build 5'

from all the dfm's its fine - well no more than the standard problems I
expect with an alteration of this magnitude. >>

Wow, that's really weird.  It should just ignore that type of issue and
continue on since the name and type of the propery hasn't changed, just the
value.

Ah, just looked in EDB and I changed the implementation to no longer have a
write property setter since the newer IDE's allow for showing read-only,
published properties.  That's probably what is doing it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Add it in to the DBISAM to ElevateDB hints

Roy Lambert