Troubleshooting
Partial username or password logs into FM Chat
FM Chat uses the FileMaker find method to log users in. One issue is that, as written, the find script will match partial usernames or passwords. Fortunately, this is an easy fix that just requires modifying two lines in the "SignIn" script.
In the "Set Field" steps on lines 15 and 16, add an equals sign (=) to the value as highlighted below:
=\"" & System::USERNAME_ENTRY & "\""]
=\"" & System::PASSWORD_ENTRY[2] & "\""]
If you're also using FMChat in FileMaker Go, make sure to also update the same script in the FMChatGo file.
Keep in mind, though, that FMChat does not come with any field or record level security enabled and is only intended to provide a process to open up the correct chat user. To ensure each user is only able to access their own chat records, FileMaker access privileges should be implemented. For more information see our Security documentation.
Growl not registering on 64-bit Windows
Since Growl for Windows is a 32-bit application, it will be installed in the "Program Files (x86)" folder on 64-bit systems. If you'd like to make FMChat compatible with Growl on both 32-bit and 64-bit operating systems, you can add a step to check for Growl in the "Program Files (x86)" installation path.
Inside the "If [Get (LastError_ and $register = 1]" statement on line 34 of the "DisplayGrowlNotice..." script, add the highlighted lines as shown in the screenshot below. For line 36, just copy the "Send Event" step from line 33 and only add " (x86)" to the file path in the let statement.
Need Help?
Our products are designed so you can integrate them into your own FileMaker solutions yourself following the instructions in our online documentation, and our team is happy to provide any guidance you need at no additional charge. So please don't hesitate to reach out if you get stuck--we can likely get your integration unstuck with a quick phone call or email.
Alternatively, our trained and certified developers can do your integration for you from start to finish. Just pick up our minimum five-hour implementation package and send us your file (more complex integrations may require more time).
We can also help you build custom features in any FileMaker solution that involves one or more of our products, including customized deployments of SeedCode Complete. For these types of projects that involve custom-built features, please get in touch to discuss the details so we can give you an estimate of the cost and timeline.
