Jump to content

Cut it out with the nulls already


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

Recommended Posts

I'm trying to deal with a SQL database (over which I have no structural control) via ODBC. In this database there are numerous fields which are to remain empty the great majority of the time, but they are configured to not allow null values. Instead, an empty string ('') must be used.

So far as I can tell, FileMaker doesn't think very highly of that tactic, and I am slowly being driven mad. Why are you even touching those fields, when they are unmodified and not even on the layout, FileMaker? Why?

If anybody can proffer a method to make FileMaker send an empty string that would be grand. Or make it stop updating unmodified fields. That'd work too.

Also, the fact that the Execute SQL script step doesn't list DSNs on the FileMaker server puzzles me deeply. Throw me a bone, here.

Link to comment
Share on other sites

This topic is 5052 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.