Hi!
My company implemented an in-house computer system that links up the work of
all major departments 10 years ago, using Paradox. Currently, we are still
using Paradox 10, and we are thinking of migrating to MS SQL 2000 server.
Is there any way to export the Paradox tables to the MS SQL 2000 server,
while continue using the ObjectPAL codings that we have already developed?
That is, using ObjectPAL to interact with the MS SQL table, instead of
Paradox table. Is there such a way? Otherwise, if we re-do all the codings i
n
Visual Basic, or other languages, it would be tedious. Or is there any way t
o
convert the ObjectPAL codings to other languages that support MS SQL?
Please advise.
Thank you.I've found out the way to connect to the MS SQL 2000 server using Paradox. I
just define a new alias first, and connect to it and perform a executeSQL
statement, which can allow me to interact with the tables in the SQL 2000
server. But there's an issue, would it then not be storing real-time
information in the server unless the user press a Save button, or something
like that in the interface? Won't this result a lot of other problems like
inconsistency, concurrency and etc?
"wrytat" wrote:
> Hi!
> My company implemented an in-house computer system that links up the work
of
> all major departments 10 years ago, using Paradox. Currently, we are still
> using Paradox 10, and we are thinking of migrating to MS SQL 2000 server.
> Is there any way to export the Paradox tables to the MS SQL 2000 server,
> while continue using the ObjectPAL codings that we have already developed?
> That is, using ObjectPAL to interact with the MS SQL table, instead of
> Paradox table. Is there such a way? Otherwise, if we re-do all the codings
in
> Visual Basic, or other languages, it would be tedious. Or is there any way
to
> convert the ObjectPAL codings to other languages that support MS SQL?
> Please advise.
> Thank you.
No comments:
Post a Comment