<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>Thank you for the input. Exactly what I needed to know! I appreciate your time and effort taken to respond.<div><br></div><div>Bests,</div><div><br></div><div>mark-></div><br>Paul McNary <pmcnary@cameron.net> wrote:<br>Fairlight wrote:<br>> Confusious (Richard Kreiss) say:<br>> <br>>> Mark,<br>>><br>>> Take a look at the Filepro web-site description on the 5.7 features. <br>>> <br>><br>> "fP+MySQL offers the user MySQL capability interfaced to filePro Plus.<br>> Read/Write from filePro or modify from external source."<br>><br>> Seriously? That's the best they can do in telling me if it's suitable for<br>> my needs? What do they mean -exactly- by "modify from external source"?<br>> Modify -what- from -what kind- of external source?<br>><br>> Folks, seriously...you need someone who can write decent documentation.<br>> What's there is a bad joke.<br>><br>> mark-><br>> _______________________________________________<br>> Filepro-list mailing list<br>> Filepro-list@lists.celestial.com<br>> Subscribe/Unsubscribe/Subscription Changes<br>> http://mailman.celestial.com/mailman/listinfo/filepro-list<br>><br>><br>> <br>I have been evaluating it for several months. It is what I needed and <br>wanted.<br>You have a mySQL table and want to use it in the same way you use a native<br>filePro table from within filePro. Define screens, reports, processing, and<br>all works fine. Updating, adding new records, deleting all works as I <br>expected<br>it to. I have not tried playing with filePro auto indexes. There are <br>some limitations<br>documented. One time manual indexes, doesn't appear to have any limitations<br>in the filePro context.<br><br>You do have the ODBC limits of 254 columns(fields) and inability to <br>directly using<br>Text/Image (Blob) fields. 999 character field length limit. I can deal <br>with these<br>in other ways if I need them.<br><br>But it does gives excellent interoperability between filePro and mySQL.<br>It was the major reason I finally upgraded to fP 5.7 after 20 years of <br>fP 4.5.<br>You do need an auto-increment field in the mySQL table, (which you <br>should have anyhow).<br>That is totally true but it makes the record number concept from fP <br>easier to relate.<br>I don't need it to be different, so definitely not a complaint. If you <br>have the auto-increment<br>field, it auto-maps the file with define files.<br><br>Makes a beautiful quick and dirty front-end for mySQL for many projects.<br>Data entry screens, ad-hoc filePro reports, filePro processing. Ability <br>to use<br>the mySQL table in programs outside filePro.<br><br>It is what I wanted and what I got.<br><br>So I am extremely happy with it.<br><br>pmcnary@cameron.net<br><br> </body>