×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

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

Migrating Paradox 9 Memo Fields to MS SQL Server

Migrating Paradox 9 Memo Fields to MS SQL Server

Migrating Paradox 9 Memo Fields to MS SQL Server

(OP)
Hello,

I am porting a 10 year old Paradox application (presently in Paradox V9) over to VB.Net/ADO.Net/MS SQL Server 2005.  The old application has a fair bit of legacy data, most of which I have been able to export to delimited text files and import into SQL Server via some VB/SQL routines.  

However, several of the Paradox tables have (F) Formatted Memo fields, which are not stored in the Paradox table proper, but in external .MB files.  When the Paradox export is done, the Memo fields are not included as an exported column.

The Paradox documentation indicates that a Formatted Memo field can only be converted to a Memo or Binary field, both of which are also stored externally.  I've tried adding a large Alpha field to the tables in question then running a Paradox SQL command with a CString() cast to set the new field equal to the Memo field - but no go - Paradox SQL will not accept the command.

I have not tried writing a Paradox PAL routine with TCursors, trying to set a new Alpha field equal to the existing Memo field - don't know if that would work or not.

Anyhow, sorry for the long post, but I am wondering, has anyone run into this problem and have you found a good solution for getting Memo field data into a SQL text column?

Thank You,
Dale

RE: Migrating Paradox 9 Memo Fields to MS SQL Server


I've seen this question addressed several times, and have NEVER seen a solution.

You might try the client_server group over on pnews; LOTS of folks with extensive Paradox AND SQL experience.

news://pnews.thedbcommunity.com/pnews.paradox-client_server

There is also a web site with connections to the above in HTML rather than news reader: http://www.thedbcommunity.com/index.php?option=com_content&task=view&;id=14&;Itemid=43

Best of luck.

Tony McGuire
"It's not about having enough time; we have the rest of our lives.  It's about priorities."

RE: Migrating Paradox 9 Memo Fields to MS SQL Server

(OP)
Tony,

Thanks for the feedback.  Even if there is no real solution, just knowing that I didn't miss out on a known fix makes me feel better.  Maybe I'll check in with the group you mentioned.  

Thanks again,
Dale
 

RE: Migrating Paradox 9 Memo Fields to MS SQL Server

How are you importing the data to sql server?

I have a Paradox application that had formatted memo fields that I converted to sql server with little to no problem.

The first thing I had to do was convert the Formatted Memo field to a Memo field. I used Access as an intermediate import tool because Sql Server 2005 does not import Paradox directly.

I imported my Paradox data into Access from Access, then I imported the Access Database into Sql Server using the Sql Server Management Studio. Everything imported perfectly including the memo fields.

I tried several different import options and found Access worked the best and fastest for me. It also helped me find data errors in my Paradox database such as null values in key fields that are allowed in Paradox and are not in Access and Sql Server.

I also have a 20 year old Paradox application that I am converting to Vb.net, It's taken almost 2 years but it should be done soon and should last another 20 years, good luck with your project.

I hope this helps
Perrin

RE: Migrating Paradox 9 Memo Fields to MS SQL Server

Quote:


I have a Paradox application that had formatted memo fields that I converted to sql server with little to no problem.

But then you said you converted to memo.  Which means you destroyed all formatting, doesn't it?  Which means the 'little to no problem' wasn't exactly.

Tony McGuire
"It's not about having enough time; we have the rest of our lives.  It's about priorities."

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