Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Paradox (v9) to SQL Server

Paradox (v9) to SQL Server

Paradox (v9) to SQL Server

We're attempting to switch the back end of our large financial application over to SQL Server (2005).

I'm just at the experiment stage.

I have created a SQL table identical in structure to my paradox one.  Yet when I attempt to attach a TCursor, I get either a GPF or Paradox closes instantly and disappears completely without warning.  Wow!  If it can't even do this much without exploding, then I'm in trouble

Any clues?
According to everything I've read, this should be a perfectly feasible project.


RE: Paradox (v9) to SQL Server

I have heard that this can be a simple process, although I've yet to see it.

I have a Paradox app that I am in the process of converting to Vb.net and Sql Server 2005 and I found what worked best for me was to do a 2 stage import into sql. I first imported the Paradox tables into Access, then imported the Access tables into Sql Server. Sql used to be able to import Paradox tables directly but Sql 2005 doesn't. I does however imports Access tables nicely. I found that Sql is very strict with field structures and RI where as Paradox and to some extend Access is fairly flexible, for example Paradox allows nulls in secondary key fields where as Sql doesn't. I found it also helped to remove the keys and RI from the tables before importing them and setting that up again under Sql Server.

Good Luck

RE: Paradox (v9) to SQL Server

Hi Perrin,

Thanks for your reply.  It's like a morgue in this forum nowadays.

Anyway, have come a little further now.

1.  Have written a paradox utility to create tables and then copy the data - bearing in mind all that you said above re no null keys etc. (I never use inbuilt RI)
2.  I was just finishing that utility off when I discovered "fullConvert"  and realised I'd been wasting my time.  A great tool, does the job in a jiffy with little fuss.  Here's the url. Download a trial.


And if you're in the UK the exchage rate is great at the moment - cheap as chips!



RE: Paradox (v9) to SQL Server


It has gotten a little dusty around here, it's a shame because Paradox was a great program.

Thanks for the tip on fullConvert, I had been looking for a conversion program and I hadn't come across fullConvert. I just tried it and it looks great. Much easier than what I had been doing.


RE: Paradox (v9) to SQL Server

Thank you Tony, I wondered where everybody had gone..

Just so you know, switching over to SQL back-end will extend the life of my paradox system in the city of london by years.  I love Paradox.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close