I'm not aware that FM ever asks the user to save their data. My understanding, and I could be wrong, but FM commits the record when the user exits the field.
In the past, I've had users create new records but leave the cursor in the last field they entered data into. FileMaker is pretty touchy about network interruptions and occasionally it will disconnect. In those cases, we would lose data. The solution is to make sure your users exit all the fields by clicking somewhere in the layout that's not a field or simply going to the next or previous record when they are done entering data.
Fm asks user to save data if you want by clicking the option in the layout option. if this option is not activate fm saves data automatically.
Sorry, i explained it bad, is just the opossite, by clicking this option fm saves data automatically.
Well I'll be ... learn something new every day.
Thanks for posting! As of this time, there are no known issues between Windows XP sp3 and saving layout changes.
Just to make sure that we're on the same page: the user is making changes in Layout Mode but sometimes will not get prompted to save his changes even though Layout Options > Save Layout changes automatically (do not ask) is not checked.
I went ahead and tried reproducing your issue here but was unsuccessful. I am running Windows XP sp3 and FileMaker Pro Advanced 9v3 as are some of my colleagues and have not come across any issues. What is the benchmark for unsaved data? I tried a test of 30 changes, closed the file, and tested 30 changes again; FileMaker prompted me to save data both tests.
Also, is the user making Layout changes on the live FileMaker Server-hosted database? While the software allows this, it is recommended that the database is taken off line and the database changes are made locally in a copy of FileMaker Pro. This can cut down the chance of your database file getting damaged/corrupt.
A good test might include trying a test database and re-creating the issue based off of the issue's benchmark. I would try this test locally on a FileMaker Pro machine. If everything seems okay, try a compacted copy or clone of your original database and re-test locally.
Is it possible the user is clicking 'Do not save' by accident?
Let me know how it works out.
Hi, ts_turtle, thank you for your answer.
I don´t know exactly the details about how the user makes it.
I´m the programmer of the solution, they only use it and don´t make any changes on the layout.
I don´t know exactly the conditions in wich filemaker crashes , i only know what the user has told me.
That´s the reason why i was asking about any problem between Fm and xp service pack 3.
Thanks for replying. Is it possible to get the user's input on the issue? (they could answer in an email or post here) If you just wanted to know if there were any existing issues with FileMaker Pro 9 and Win XP sp3, then I hope I answered your question appropriately in my previous post; let me know if you need any further clarification.
If the user would like to work toward a resolution, let's have the user offer some insight by answering the questions I had posted.
Either way, I am happy to help!