Migrating from BDE to DOA ?

[royj]

I have 3 applications I consider migrating to DOA (Delphi5 Enterprise ed., BDE 5.0.0.38 and 5.1.1.1, Woll2Woll components wherever possible (tables, queries, editors, grids etc.), Oracle 7.3.4 and 8.1.7, Working with single connection to one database).

What should I look for in the existing code that could be problematic / time consuming to migrate to DOA. Any standard Delphi components or existing programming code that I should be aware of that will require "re-configuration"?

Do I have to make changes to each and every dataset/query, or could I make chances only a few places (like the database component...)

The clients have a mix of Oracle7 and 8 client for SQL*Net - would that be a problem?

How much time could be expected (wild guess) to migrate an application with 30 forms, 10 TwwTables, 15 TwwQueries?

Roy

 

[Marco Kalter]

You will have the most problems if you have used a "TTable approach". SQL Servers don't really like the TTable component, because its concepts are not really appropriate for SQL, which is a set oriented language. If you use the 10 TwwTables to navigate through large tables, then you will have to do some redesign...

------------------
Marco Kalter
Allround Automations

 

[royj]

Originally posted by mkalter:
You will have the most problems if you have used a "TTable approach". SQL Servers don't really like the TTable component, because its concepts are not really appropriate for SQL, which is a set oriented language. If you use the 10 TwwTables to navigate through large tables, then you will have to do some redesign...

I have seen svereral people saying this, but is it really slower to have a TTable that gets a filter applied first (narrows down to the few rows I am interessted in), and then opened/activated? The alternative is to make a Query with the same where clause as the table filter...

I understand your concern if the table is activated first and _then_ filtered...

Roy

 

[Marco Kalter]

This example probably works just fine, because you are treating the TTable as a TQuery. This code can easily be replaced. But if you use an active TTable to search for or navigate to records, then it will be a different ball game.

------------------
Marco Kalter
Allround Automations