I have the daunting task of moving all of my applications, which is approx
30 or so, to Delphi 2006 and DBISAM 4.22.  I currently use D7 Pro and DBISAM
3.26 in local and C/S modes.

This seems like a humongous undertaking.

Is there an easy path?  Can older 3.26 apps that are near retirement connect
to a 4.22 server?  I have a few older ISAPI.DLL (Intraweb 6.23) apps that I
use to just read info and display in browser etc.. I don't want to upgrade
Intraweb to D2006..

Any tips to help encourage me would be welcomed

TIA,

--
John

JohnE wrote:
> I have the daunting task of moving all of my applications, which is
> approx 30 or so, to Delphi 2006 and DBISAM 4.22.  I currently use D7
> Pro and DBISAM 3.26 in local and C/S modes.
>
> This seems like a humongous undertaking.

Not really

> Is there an easy path?

Of course: just do it! The connecting stuff maybe needs some rework, 15
minutes or so. Then look for MEMORY in SQL statements and ' or " in SQL and
Filters. That's more or less all. With some experience, you can switch an
application from 3 to 4 in hours.

> Can older 3.26 apps that are near retirement
> connect to a 4.22 server?

No.

> I have a few older ISAPI.DLL (Intraweb
> 6.23) apps that I use to just read info and display in browser etc..
> I don't want to upgrade Intraweb to D2006..

Then don't. I do most of my work with Delphi 5.

Ralf

> Then don't. I do most of my work with Delphi 5.


Haha.. well, I bought D2006 Enterprise.  I also do work with .Net and
Asp.net in particular, so it'd be nice to consolidate my environment.  I
downloaded Vmware today, maybe give that a shot.

John

JohnE wrote:
>> Then don't. I do most of my work with Delphi 5.
>
>
> Haha.. well, I bought D2006 Enterprise.  I also do work with .Net and
> Asp.net in particular, so it'd be nice to consolidate my environment.

Well, if you don't want to develop your older ISAPI modules with D2006, then
the only solution I can offer i´s: "Don't do that"

Ralf

Any experience with handlng ReportBuilder when moving from V3 to V4?  I
imagine with the quoting change that potentially ReportBuilder reports could
be significantly affected?

Thanks

Alex

"Ralf Mimoun" <nospam@rad-on.de> wrote in message
news:FAE1C8F5-3816-4647-A978-C3B0BF96E1F2@news.elevatesoft.com...
> JohnE wrote:
>>> Then don't. I do most of my work with Delphi 5.
>>
>>
>> Haha.. well, I bought D2006 Enterprise.  I also do work with .Net and
>> Asp.net in particular, so it'd be nice to consolidate my environment.
>
> Well, if you don't want to develop your older ISAPI modules with D2006,
> then the only solution I can offer i´s: "Don't do that"
>
> Ralf

Al Vas wrote:
> Any experience with handlng ReportBuilder when moving from V3 to V4?
> I imagine with the quoting change that potentially ReportBuilder
> reports could be significantly affected?

Not here. I had not one problem with RBuilder changing from 3 to 4.

Ralf

Quoting change?

> Quoting change?

3.26 allowed quotedstr (single) around identifiers however 4.x insists on
ansiquotedstr ie "E:\Path\MyTable" vs singled.  We placed all of our calls
in a function to minimize the conversion effort.

hth.  Donat.

John,

<< Is there an easy path?  Can older 3.26 apps that are near retirement
connect to a 4.22 server?  I have a few older ISAPI.DLL (Intraweb 6.23) apps
that I use to just read info and display in browser etc.. I don't want to
upgrade Intraweb to D2006.. >>

Besides the contributions already made, I would strongly suggest reading
thoroughly these sections of the manual:

http://www.elevatesoft.com/dbisam4d5_changes.htm
http://www.elevatesoft.com/dbisam4d5_new_features.htm

The main changes can be summarized as this:

1) Table format
2) Table creation/restructuring
3) SQL quotes - identifiers now require double-quotes instead of
single-quotes, and constants require single-quotes
4) The new handling of in-memory tables via the "Memory" database instead of
the MEMORY keyword and InMemory property

--
Tim Young
Elevate Software
www.elevatesoft.com