filepro to sql

[Ryan Powers]

>I was talking about if your filePro data doesn't map directly to your SQL
tables.  Does your program just recreate the filePro >maps as SQL tables, or
can you map the filePro fields to specific table fields?

No, it's a straightforward conversion and it will refuse to use any MySQL
table that already exists, so naturally there is no mapping involved.

>Oh - and I did mention in another post today that my own method for
migrating filePro data to MySQL does fieldname cleanup and >edit conversion,
so I'm definitely familiar with the issues :)  Why don't you find type
conversion worth the trouble?  I found it >pretty easy to create rules for
type conversion and data filters to scrub with.

I've done it more than a few times and it is practically impossible to
perfect that type of process. There are always going to be exceptions e.g.
You have a mm/dd/yy edit and somebody types in 4.23.09. You're going to have
to include things like that in your data scrubbing. I wanted to keep this
simple and free of complications in both code and user experience.

This is just something that I spent some time on and wanted to put out there
to see if it would be a useful product. Data scrubbing will certainly come
up again, but it’s a different ball of wax, or can of worms depending on
your point of view.


---
Ryan Powers
Bulldog Software, Inc.
http://www.bulldogsoftware.com