<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The second problem is that filePro allows duplicate field names.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It isn’t a straightforward transfer because that would be
impossible. There are several field changes but the data remains intact, albeit
the<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>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<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>do a text transfer and then clean and convert the field types in
MySQL once you have them in the tables.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>---<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ryan Powers<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bulldog Software, Inc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a href="http://www.bulldogsoftware.com/"><span
style='color:blue'>http://www.bulldogsoftware.com</span></a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
filepro-list-bounces+ryanx=indy.rr.com@lists.celestial.com
[mailto:filepro-list-bounces+ryanx=indy.rr.com@lists.celestial.com] <b>On
Behalf Of </b>Tyler<br>
<b>Sent:</b> Wednesday, April 22, 2009 4:28 PM<br>
<b>To:</b> filepro-list@lists.celestial.com<br>
<b>Subject:</b> Re: Filepro-list Digest, Vol 63, Issue 23<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>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.<br>
<br>
<br>
--<br>
Tyler Style<br>
<a href="http://www.malthusian-solutions.com/" target="_blank">http://www.malthusian-solutions.com</a><o:p></o:p></p>
<p class=MsoNormal>Date: Wed, 22 Apr 2009 15:28:44 -0400<br>
From: "Ryan Powers" <<a href="mailto:ryanx@indy.rr.com">ryanx@indy.rr.com</a>><br>
Subject: RE: filepro to sql<o:p></o:p></p>
<div id=":1b4">
<p class=MsoNormal><br>
Within the next few days I'll be announcing fp2mysql which is a console<br>
based app written in C# which<br>
<br>
asks a few questions and then transfers the entire filePro key file into a<br>
new MySQL table.<br>
<br>
<br>
<br>
For the most part, the only requirements are MyODBC, .NET, and a filePro key<br>
file. It will be out in demo form<br>
<br>
and then a full version will follow by the end of the month.<br>
<br>
<br>
<br>
---<br>
<br>
Ryan Powers<br>
<br>
Bulldog Software, Inc.<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>