So just freshly installed the new 4.31 along with addon tools.  Compiled and installed the utility package (had to change VCL50 to VCL)

Now trying to compile dbsys first and having issues.

First can't find FastMM4
Next can't find QuickRpt then dbisamut, then dbisamct

Getting errors on TVersionInfo, TEngineSettings, etc...

What am I missing here?

The utilities have not been updated with more recent versions of delphi.

There is note on download page "The source code for these utilities is compatible with Delphi 5 only and may need some minor changes if compiled with a later version of Delphi."

Raul

<<
Andrew H. Grilk wrote:

What am I missing here?
>>

Ok well the last one I compiled was in 2007 with Delphi 2006 (not Delphi 5) I think it was 4.25 and that worked.  Has anyone been able to compile it with Delphi XE?

Raul wrote:


The utilities have not been updated with more recent versions of delphi.

There is note on download page "The source code for these utilities is compatible with Delphi 5 only and may need some minor changes if compiled with a later version of Delphi."

Raul

<<
Andrew H. Grilk wrote:

What am I missing here?
>>

Andrew,

Delphi 2006 was the last one with Quick Reports (QuickRpt) I guess (I'm not
sure about D2007), so unless you have Quick Reports Pro you wont be able to
compile it with XE.

--
Fernando Dias
[Team Elevate]

Ok here is my issue.  I used a customized DBEngine signature for the product we built.  Now making changes the engine will be using 4.31 however the srvadmin and dbsys I have were compiled with 4.25 using my customized DBEngine.  Assuming there are VAST differences in the engine I would need the same version of dbsys and srvadmin with my DBEngine to manipulate the released code.  Are there any drawbacks to using the 4.25 build I have with the 4.31 engine especially for things like table repair and such?

"Fernando Dias" wrote:

Andrew,

Delphi 2006 was the last one with Quick Reports (QuickRpt) I guess (I'm not
sure about D2007), so unless you have Quick Reports Pro you wont be able to
compile it with XE.

--
Fernando Dias
[Team Elevate]

Do not use older dbsys - there was a significant internal blob change as of 4.28 so definitely don't use mix mix anything older like 4.25 with newer files.

The dbsys.ini file does let you specify engine signature (Signature=DBISAM_SIG is default entry there) - see if that is enough. The dbsys ini itself is in the user local app settings folder (on XP for me it's in C:\Documents and Settings\raul\Local Settings\Application Data\Elevate Software\Database System Utility)

Raul

<<
Andrew H. Grilk wrote:

Ok here is my issue.  I used a customized DBEngine signature for the product we built.  Now making changes the engine will be using 4.31 however the srvadmin and dbsys I have were compiled with 4.25 using my customized DBEngine.  Assuming there are VAST differences in the engine I would need the same version of dbsys and srvadmin with my DBEngine to manipulate the released code.  Are there any drawbacks to using the 4.25 build I have with the 4.31 engine especially for things like table repair and such?
>>

Will check it out.  Is there also a setting for engine signature for the srvAdmin?  Also since the internal blob changes...I have MANY tables out there created in 4.25 how should they be updated since I will now be compiling with 4.31?
--


Raul wrote:

Do not use older dbsys - there was a significant internal blob change as of 4.28 so definitely don't use mix mix anything older like 4.25 with newer files.

The dbsys.ini file does let you specify engine signature (Signature=DBISAM_SIG is default entry there) - see if that is enough. The dbsys ini itself is in the user local app settings folder (on XP for me it's in C:\Documents and Settings\raul\Local Settings\Application Data\Elevate Software\Database System Utility)

Raul

<<
Andrew H. Grilk wrote:

Ok here is my issue.  I used a customized DBEngine signature for the product we built.  Now making changes the engine will be using 4.31 however the srvadmin and dbsys I have were compiled with 4.25 using my customized DBEngine.  Assuming there are VAST differences in the engine I would need the same version of dbsys and srvadmin with my DBEngine to manipulate the released code.  Are there any drawbacks to using the 4.25 build I have with the 4.31 engine especially for things like table repair and such?
>>

I don't think so but as i recall last time i tried to recompile it you just need to change couple of string to ansistrings and it should compile just fine. So this one might be easy enough to recompile.

Raul

<<
Andrew H. Grilk wrote:

Will check it out.  Is there also a setting for engine signature for the srvAdmin?  Also since the internal blob changes...I have MANY tables out there created in 4.25 how should they be updated since I will now be compiling with 4.31?
--
>>

Andrew,

<< Also since the internal blob changes...I have MANY tables out there
created in 4.25 how should they be updated since I will now be compiling
with 4.31? >>

There is no update requirement - you simply can't mix the two.  The reason
for the change was a bug fix, so it wasn't something that was planned like a
format change between major releases.

--
Tim Young
Elevate Software
www.elevatesoft.com

This puts me back to square one.  UGH!  At this point I will need to recompile everything in new DBISAM version.  Is there an upgrade function that can be run on existing tables or will I need to completly recreate them?

"Tim Young [Elevate Software]" wrote:

Andrew,

<< Also since the internal blob changes...I have MANY tables out there
created in 4.25 how should they be updated since I will now be compiling
with 4.31? >>

There is no update requirement - you simply can't mix the two.  The reason
for the change was a bug fix, so it wasn't something that was planned like a
format change between major releases.

--
Tim Young
Elevate Software
www.elevatesoft.com