I created a test database and I could not replicate your issues. Make a brand new test file and create the two fields as stated above. Do not copy anything from your current database to the new test file. If the test works then there could be corruption in your old database. Run Recover on the database to check for errors.
Thanks for the response. I did what you suggested and started a new DB and got the same results you did.
If this is a corruption in my database I am scared, because I just started development on this project. It has three simple tables and some sample data. One table contains 6 records.
I will restart my development and test these features out early and often.
FWIW, I forgot to mention I am working with FM11 pro.
I would suggest making daily backups, so you will not lose your work. It may not be corruption, but it is possible and that's why you should run Recover on the file to check for errors.
Here is a link on how to avoid file corruption http://help.filemaker.com/app/answers/detail/a_id/4426/~/corrupt-%2F-damaged-files%3A-how-to-avoid-the-need-for-recovery
Thanks for the info Mr. Chamblee,
My critical DBs are on dropbox so I have multi-version restore capability. It's painful with the dropbox syncs, but it's worth it. Some of my less critical work is backed up on mozy.
I also dump all data into .cvs files on an irregular basis so that I can keep an eye on things and I have set up the DB in a way that I can clean it for runtime distribution and repopulate the data with .cvs files if this is appropriate.
I will try to replicate the serial stuff. I doubt it was a data corruption since there were no funny shutdowns while the DB was in operation and the DB was exceedingly simple.
I appreciate the insights.