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.
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.
Showing posts with label paradox. Show all posts
Showing posts with label paradox. Show all posts
Tuesday, March 20, 2012
Paradox, ObjectPAL, MS SQL 2000
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.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.
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.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.
Paradox, ObjectPAL, MS SQL 2000
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.
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.
paradox to sql server 2005
Hi,
I have been told, I will have to transfer some paradox data into sql server 2005.
What is the best way to do this? i.e. if SSIS can be used, then what will be the source? I ask because there does not seem to be a source for Paradox.
Any thoughts please?
ThanksParadox came with an ODBC driver. Install the driver and use that as your source.|||
I have been told, I will have to transfer some paradox data into sql server 2005.
What is the best way to do this? i.e. if SSIS can be used, then what will be the source? I ask because there does not seem to be a source for Paradox.
Any thoughts please?
ThanksParadox came with an ODBC driver. Install the driver and use that as your source.|||
Do you mean in the DataFlow sources there should be ODBC sources? If so, how do I get it to appear there? Do I need to install ODBC driver first? where do I get it from please?
Thanks
|||arkiboys wrote:
Do you mean in the DataFlow sources there should be ODBC sources? If so, how do I get it to appear there? Do I need to install ODBC driver first? where do I get it from please?
Thanks
Please reread Tom's post. If you can connect to Paradox, you should already have th ODBC driver loaded. Using a DataReader Source in your Data Flow, you should be able to see the Paradox ODBC driver listed as an option for you. If you don't then you need to work with the vendor of Paradox to get the ODBC driver.
Paradox table import in SQL Server 2000
I need to import any paradox tables in SQL Server 2000, but i'm having
troubles with char conversion:
Does anyone have any idea about why all accented chars in source paradox
table turn into other chars in the new SQL Table:
in paradox turns into in SQL
" " " " " "
" " " " " "
" " " " ? " "
" " " " " "
" " " " " "
Any hints on what should i trim to correcty this behavior?
Thanks
Mario
you need to pick another collation. What collation is DTS automatically
selecting? It looks like you should be using French.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:cguq57$vv4$1@.news.ngi.it...
> I need to import any paradox tables in SQL Server 2000, but i'm having
> troubles with char conversion:
> Does anyone have any idea about why all accented chars in source paradox
> table turn into other chars in the new SQL Table:
> in paradox turns into in SQL
> " " " " " "
> " " " " " "
> " " " " ? " "
> " " " " " "
> " " " " " "
> Any hints on what should i trim to correcty this behavior?
> Thanks
> Mario
>
|||Hello Hilary,
i couldn't find a way to see which collation is my DTS automatically
selecting, i can only imagine it's Latin General since i've changed nothing
in default settings and i'm in italy.
Anyway it looks more like it's a problem with settings on OEM/ANSI
translation settings, but even in this case i couldn't find a way to set
such a setting.
Mario Cappa
"Hilary Cotter" <hilaryk@.att.net> ha scritto nel messaggio
news:ezjkYZojEHA.3724@.TK2MSFTNGP11.phx.gbl...
> you need to pick another collation. What collation is DTS automatically
> selecting? It looks like you should be using French.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:cguq57$vv4$1@.news.ngi.it...
>
|||how are you importing the table? Is this through a DSN? If so what collation
sequence are you using. I think you should be using ANSI.
Also check the collation of the table which DTS created. Do a sp_help
TableName using Query Analyzer.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:cgvh2s$848$1@.news.ngi.it...
> Hello Hilary,
> i couldn't find a way to see which collation is my DTS automatically
> selecting, i can only imagine it's Latin General since i've changed
nothing[vbcol=seagreen]
> in default settings and i'm in italy.
> Anyway it looks more like it's a problem with settings on OEM/ANSI
> translation settings, but even in this case i couldn't find a way to set
> such a setting.
> Mario Cappa
> "Hilary Cotter" <hilaryk@.att.net> ha scritto nel messaggio
> news:ezjkYZojEHA.3724@.TK2MSFTNGP11.phx.gbl...
paradox
>
|||I'm using ANSI on SQL but i'm not sure the setting is the same on Paradox
table
Table is imported through Paradox 5.x OLE DB drivers and collation sequence
results as Latin1_General_CI_AS
"Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
news:Our0dmqjEHA.556@.tk2msftngp13.phx.gbl...
> how are you importing the table? Is this through a DSN? If so what
collation[vbcol=seagreen]
> sequence are you using. I think you should be using ANSI.
> Also check the collation of the table which DTS created. Do a sp_help
> TableName using Query Analyzer.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:cgvh2s$848$1@.news.ngi.it...
> nothing
automatically[vbcol=seagreen]
having
> paradox
>
|||how about trying the international setting on your dsn?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:ezhKiuqjEHA.704@.TK2MSFTNGP09.phx.gbl...
> I'm using ANSI on SQL but i'm not sure the setting is the same on Paradox
> table
> Table is imported through Paradox 5.x OLE DB drivers and collation
sequence[vbcol=seagreen]
> results as Latin1_General_CI_AS
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
> news:Our0dmqjEHA.556@.tk2msftngp13.phx.gbl...
> collation
set
> automatically
> having
>
|||I solved my problems after i could find paradox tables native language and
change it to Western Europe ANSI
Thanky you for your suggestions
Mario
"Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
news:%23HjsoMwjEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> how about trying the international setting on your dsn?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:ezhKiuqjEHA.704@.TK2MSFTNGP09.phx.gbl...
Paradox[vbcol=seagreen]
> sequence
automatically
> set
>
troubles with char conversion:
Does anyone have any idea about why all accented chars in source paradox
table turn into other chars in the new SQL Table:
in paradox turns into in SQL
" " " " " "
" " " " " "
" " " " ? " "
" " " " " "
" " " " " "
Any hints on what should i trim to correcty this behavior?
Thanks
Mario
you need to pick another collation. What collation is DTS automatically
selecting? It looks like you should be using French.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:cguq57$vv4$1@.news.ngi.it...
> I need to import any paradox tables in SQL Server 2000, but i'm having
> troubles with char conversion:
> Does anyone have any idea about why all accented chars in source paradox
> table turn into other chars in the new SQL Table:
> in paradox turns into in SQL
> " " " " " "
> " " " " " "
> " " " " ? " "
> " " " " " "
> " " " " " "
> Any hints on what should i trim to correcty this behavior?
> Thanks
> Mario
>
|||Hello Hilary,
i couldn't find a way to see which collation is my DTS automatically
selecting, i can only imagine it's Latin General since i've changed nothing
in default settings and i'm in italy.
Anyway it looks more like it's a problem with settings on OEM/ANSI
translation settings, but even in this case i couldn't find a way to set
such a setting.
Mario Cappa
"Hilary Cotter" <hilaryk@.att.net> ha scritto nel messaggio
news:ezjkYZojEHA.3724@.TK2MSFTNGP11.phx.gbl...
> you need to pick another collation. What collation is DTS automatically
> selecting? It looks like you should be using French.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:cguq57$vv4$1@.news.ngi.it...
>
|||how are you importing the table? Is this through a DSN? If so what collation
sequence are you using. I think you should be using ANSI.
Also check the collation of the table which DTS created. Do a sp_help
TableName using Query Analyzer.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:cgvh2s$848$1@.news.ngi.it...
> Hello Hilary,
> i couldn't find a way to see which collation is my DTS automatically
> selecting, i can only imagine it's Latin General since i've changed
nothing[vbcol=seagreen]
> in default settings and i'm in italy.
> Anyway it looks more like it's a problem with settings on OEM/ANSI
> translation settings, but even in this case i couldn't find a way to set
> such a setting.
> Mario Cappa
> "Hilary Cotter" <hilaryk@.att.net> ha scritto nel messaggio
> news:ezjkYZojEHA.3724@.TK2MSFTNGP11.phx.gbl...
paradox
>
|||I'm using ANSI on SQL but i'm not sure the setting is the same on Paradox
table
Table is imported through Paradox 5.x OLE DB drivers and collation sequence
results as Latin1_General_CI_AS
"Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
news:Our0dmqjEHA.556@.tk2msftngp13.phx.gbl...
> how are you importing the table? Is this through a DSN? If so what
collation[vbcol=seagreen]
> sequence are you using. I think you should be using ANSI.
> Also check the collation of the table which DTS created. Do a sp_help
> TableName using Query Analyzer.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:cgvh2s$848$1@.news.ngi.it...
> nothing
automatically[vbcol=seagreen]
having
> paradox
>
|||how about trying the international setting on your dsn?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario Cappa" <mario.cappa@.arcott.it> wrote in message
news:ezhKiuqjEHA.704@.TK2MSFTNGP09.phx.gbl...
> I'm using ANSI on SQL but i'm not sure the setting is the same on Paradox
> table
> Table is imported through Paradox 5.x OLE DB drivers and collation
sequence[vbcol=seagreen]
> results as Latin1_General_CI_AS
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
> news:Our0dmqjEHA.556@.tk2msftngp13.phx.gbl...
> collation
set
> automatically
> having
>
|||I solved my problems after i could find paradox tables native language and
change it to Western Europe ANSI
Thanky you for your suggestions
Mario
"Hilary Cotter" <hilary.cotter@.gmail.com> ha scritto nel messaggio
news:%23HjsoMwjEHA.2340@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> how about trying the international setting on your dsn?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario Cappa" <mario.cappa@.arcott.it> wrote in message
> news:ezhKiuqjEHA.704@.TK2MSFTNGP09.phx.gbl...
Paradox[vbcol=seagreen]
> sequence
automatically
> set
>
Subscribe to:
Posts (Atom)