

Maybe you can shed some light on this for me? I’ve not had a go yet to attempt to create new entries in the MySQL database direct from FMP as I’m not to sure on the correct way to do so. Using ODBC as a live feed into Filemaker I too can amend OSC data direct from FMP with no problems at all, so long as the connection stays live.

I’m now in the process of doing the exact same thing as yourself with regards to using ODBC to interact with the online shop. We also use Filemaker as a backend to our OSC shop which we use for creating invoices and holding supplier information etc…Īt present I upload new products via easypopulate to populate the shop with new products which has always worked really well, I then use the same excel file to import the products into Filemaker. It will be able to statically and dynamically interface both our ecommerce and busines infrastrucures. If this is a reasonable solution to this problem, we can now proceed with completion of a fully operational fFleMaker Pro API to our OSC ecommerce store. Since our intentions is interface with OSC "ONLY" via our FMP application, is there any reason why I can not or should not be changing the offending tables entries from "non null" to "null"? In one such offending table (products), I went in and changed the "non null" attribute to "null" and I can now create/deleate/read/write all the records I need. I guess this is so that users of the Admin interface data entry panel enter in certain required data fields before the new record is committed. I traced this problem to the fact that some of the OSC table entires specify a "non null" value. When I try to create a new OSC records via FMP I get an ODBC create_record error on only some of the tables that I want to create a new record for some create perfectly. I can see my entire OSC database and I can read and write existing OSC records. I have successfully integrated FMP with my OSC store via ODBC. We use FileMaker Pro 9.0 for our business infrastructure and our product/inventory management.
