Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How can I resolve MySQL error 1117 when attempting to create a MySQL table to match my FileMaker database file?

0
Posted

How can I resolve MySQL error 1117 when attempting to create a MySQL table to match my FileMaker database file?

0

FileMaker versions prior to FileMaker 7 do not include a built-in mechanism to keep track of variables while running a script or calculation. Therefore many FileMaker databases contain dozens of global fields used to store this type of information. FileMaker summary and calculation fields are also handled differently within a database like MySQL. Calculation features during record insertion are usually handled via the software which is providing the interface to the database. MySQL version 5.0 will offer stored procedures and triggers in order to provide this functionality. The problem with having so many fields is that you can exceed the maximum number of columns which can be created within the MySQL table or the maximum number of bytes allowed per row of data. MySQL is one of the most generous database servers in regards to these capacities, (2364 columns per table, and max row contents of 65501 bytes) but these limits can still be exceeded by FileMaker. It is generally possible to r

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.