Very Computer

by **Peter Stromber** » Sun, 12 May 1996 04:00:00

I wonder if there is a FAQ or some such that handles converting
existing Paradox projects using a Paradox database to acces databases
living on a server RDBMS.

I've installed Oracle Workgroup Server and moved my Paradox tables
to there. Some operations gets _very_ slow compared to the pure
paradox solution. It seems like SQL Links does some really time consuming
operations in order to glue Paradox requests to Oracle7.
Some of the searches is easyily (and conviniently) converted to SQL
calls but that is not always the case.

Moving around in the dataset (eg first, last, previous and next) is
the most penalized operations. Why is this? Can I get around it. First
and last can be converted to SQL using min() and max() but that seems
not to be the most logical solution. Previous and next is not as easily
converted to SQL (as you can realize).

Is there a way for me to access the cursors in a more native manner
than the one paradox chooses automaticly?

Oh, right. I make heavy use of OPAL in my projects.

Thanx in advance for any help.
--
_/_/_/_/_/_/_/_/_/
_/ _/_/ _/
_/_/_/_/_/ _/
_/ _/ _/
_/ _/_/_/_/_/_/

by **Daniel A. Morga** » Mon, 13 May 1996 04:00:00

> I wonder if there is a FAQ or some such that handles converting
> existing Paradox projects using a Paradox database to acces databases
> living on a server RDBMS.

No. I suggest that you visit CompuServe forum 18 (SQL Link). Many of us
hang out there and the quality of support is very high. I have
personally been involved in several major projects using PdoxWin as a
front-end to Oracle 7 servers.

Quote:> I've installed Oracle Workgroup Server and moved my Paradox tables
> to there. Some operations gets _very_ slow compared to the pure
> paradox solution. It seems like SQL Links does some really time
> consuming operations in order to glue Paradox requests to Oracle7.

It is critical for speed to limit the range of records viewed by PdoxWin
to the absolute minimum. This helps both speed and stability. When you
open a form, for example, use setRange as a filtering mechanism. When
performing locates always use qLocate. There does not seem to be any
significant difference between using tCursors against Oracle tables and
writing tons of SQL code.

Quote:> Moving around in the dataset (eg first, last, previous and next) is
> the most penalized operations. Why is this? Can I get around it. First
> and last can be converted to SQL using min() and max() but that seems
> not to be the most logical solution. Previous and next is not as easily
> converted to SQL (as you can realize).

See the above answer. Never work with the complete data table. Always
limit the view.

Quote:> Is there a way for me to access the cursors in a more native manner
> than the one paradox chooses automaticly?

Yes!. Use Oracle Forms 4.5 or PowerObjects. It is an honest answer to
the question but not the answer I chose. I use PdoxWin and it is a great
solution when set up properly.

Daniel Morgan
EXE Solutions

Very Computer

Using PDX against a Server RDBMS (like Oracle)

Using PDX against a Server RDBMS (like Oracle)

Using PDX against a Server RDBMS (like Oracle)