Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 6449 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Fatal error: Cannot use object of type FX_Error as array in D:Apachehtdocsnewpubs_e.php on line 107

This error message just started appear on our newsearch page.

Posted

This has been solved for the record:

Cause - a bad character had been entered into the database. FX.php didn't like it and choked. Most likely this happened because someone copied some text from MS Word that contained the bad characters and pasted it into filemaker. This may be fixed in UTF-8.

Next point made by Chris Hansen is that all FX.php users should invoke error checking in their data.

Here is his note:

------------------------------------------------

The only way you'd see this is if you're not performing error

checking on the data that comes back from FX.php. (Gasp!) Even though you want to assume that things will always work properly, you should always do a check like this in your code:

if (FX::isError($myReturnedData)) {

...handle errors gracefully here...

}

This is a general heads up to the list: _always_ perform error checking! HTH

--Chris Hansen

This topic is 6449 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.