Filepro-list Digest, Vol 63, Issue 23

[Ryan Powers]

filePro allows you to use multiple words for field names which isn't
permitted in MySQL, so the only way I see around this is to alter them.

The second problem is that filePro allows duplicate field names.

 

It isn't a straightforward transfer because that would be impossible. There
are several field changes but the data remains intact, albeit the

edits will not be. I considered retaining the edits but I've been down that
road before and it really isn't worth the trouble. IMO it is best to

do a text transfer and then clean and convert the field types in MySQL once
you have them in the tables.

 

---

Ryan Powers

Bulldog Software, Inc.

 <http://www.bulldogsoftware.com/> http://www.bulldogsoftware.com

 

 

From: filepro-list-bounces+ryanx=indy.rr.com at lists.celestial.com
[mailto:filepro-list-bounces+ryanx=indy.rr.com at lists.celestial.com] On
Behalf Of Tyler
Sent: Wednesday, April 22, 2009 4:28 PM
To: filepro-list at lists.celestial.com
Subject: Re: Filepro-list Digest, Vol 63, Issue 23

 

Neat, but what happens if you don't want the original file structure for the
new schema?  I know our files were a mess and would not have transitioned
well directly to an RDBS.


--
Tyler Style
http://www.malthusian-solutions.com <http://www.malthusian-solutions.com/> 

Date: Wed, 22 Apr 2009 15:28:44 -0400
From: "Ryan Powers" <ryanx at indy.rr.com>
Subject: RE: filepro to sql


Within the next few days I'll be announcing fp2mysql which is a console
based app written in C# which

asks a few questions and then transfers the entire filePro key file into a
new MySQL table.



For the most part, the only requirements are MyODBC, .NET, and a filePro key
file. It will be out in demo form

and then a full version will follow by the end of the month.



---

Ryan Powers

Bulldog Software, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20090422/7b66145d/attachment.html