Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Version 3 support in Delphi 2006?
Tue, Apr 18 2006 1:52 PMPermanent Link

Wayne Showalter
I'm sure most of you have moved way past v3, but some of us are slow to upgrade. We've
made some customizations in v3 (mostly descended components) that we can't live without,
and are determined not to go through the upgrade/rework pain until unicode is available,
which v5 will provide us some day. Smile

Until then, we are stuck with v3, but would like to use DBIsam in Delphi 2006 (we're
currently using Delphi 6). Is there any support for this? Is this a daunting task if we
undertake to change v3 source ourselves to support Delphi 2006?

Wayne
Tue, Apr 18 2006 2:01 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Wayne


I think the answer is yes, if you have the DBISAM source. IIRC Tim has posted about this fairly recently - have a search of the ngs.
Roy Lambert
Tue, Apr 18 2006 5:55 PMPermanent Link

Wayne Showalter
Roy Lambert <roy.lambert@skynet.co.uk> wrote:

<Wayne


<I think the answer is yes, if you have the DBISAM source. IIRC Tim has posted about this
fairly recently - have a search of the ngs.
<Roy Lambert

I found and implemented the dbisamtb.pas and dbisamvr.inc changes from Tim, but I get a
whole host of errors that block the compile, starting with the line in dbisamcn.pas:

TPageBuffer = array [1..(PAGE_SIZE-SizeOf(TPageHeader))] of Byte;
Error: Constant expression expected

After 'fixing' that one (hard coding the sizeof(TPageHeader)), I get many many errors on
PChar and Pointer references, starting with:
[Pascal Error] DBISAMCn.pas(1473): E2397 Unsafe pointer only allowed if compiling with
{$UNSAFECODE ON}

I have not been able to fix all of them to make the compiler happy. Sprinkling in
{$UNSAFECODE ON}'s fixes most but not all of the errors. It seems like I must be missing
something big here. I admit I am a Delphi 2006 virgin. Any clue about what I MUST be missing?

Wayne
Tue, Apr 18 2006 6:04 PMPermanent Link

Wayne Showalter
I solved my own problem. I WAS missing something BIG! I was accidentally creating a VCL
for .NET application! All appears to be well in the world again!

Wayne
Tue, Apr 18 2006 6:50 PMPermanent Link

"Lance R."
Dooh.

I hate it when that happens......

lol

Lance


Wayne Showalter wrote:
> I solved my own problem. I WAS missing something BIG! I was accidentally creating a VCL
> for .NET application! All appears to be well in the world again!
>
> Wayne
>
>
Wed, Apr 19 2006 3:18 AMPermanent Link

Stuart Kelly
Hey Wayne,

> I'm sure most of you have moved way past v3, but some of us are slow to upgrade. We've
> made some customizations in v3 (mostly descended components) that we can't live without,
> and are determined not to go through the upgrade/rework pain until unicode is available,
> which v5 will provide us some day. Smile
>
> Until then, we are stuck with v3, but would like to use DBIsam in Delphi 2006 (we're
> currently using Delphi 6). Is there any support for this? Is this a daunting task if we
> undertake to change v3 source ourselves to support Delphi 2006?
>

There is no official support for DBISAM 3 using BDS/Delphi 2006.
However it is possible to get the components to compile if you have the
source.

We use DBISAM 3 with C++Builder 2006 to support our software, mostly
written in C++Builder 6.

Stuart.
Wed, Apr 19 2006 3:26 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Wayne


Not an error I'd get for two reasons 1) I didn't install .NET and 2) I don't have the DBISAM source Smiley

Roy Lambert
Wed, Apr 19 2006 11:46 AMPermanent Link

Wayne Showalter
<Not an error I'd get for two reasons 1) I didn't install .NET and 2) I don't have the
DBISAM source Smiley

<Roy Lambert

...and I have both! I'm successfully compiled and run my project using DBIsam v3 and
Delphi 2006, which makes me a very happy camper. Even the custom changes to DBIsam that we
have made were not a problem for Delphi 2006. I can now happily wait for v5...

Wayne
Image