kwhaley

Since I am using a sorted portal, the portal will not update without a commit. But since your response provoked further thought (head banging), I tried the following in my script: Crete new record, Set temporary data ("1") in each auto-validated filed (those with required value.) Commit the record. Set the field values back to null ("") Got to the first data entry field (select) It basically faked out the auto validation before the commit, then removed the faked data after the commit landing the user in the field as I had desired. With this work around, my solution seems to be functioning as it did in FM6. Perhaps a software technician could explain or provide other background about what happened during the rewrite of FM7 and why the commit came to be. (The problem with us dinosaur developers is that we learn and hold on to what we already knew- often times blinding us to newer, greater things. In my case I still remember Filemaker Plus)

I have been using Filemaker since 1986 when it was Filemaker Plus by Nashoba Systems. It was very simple flat file system that has evolved into a sophisticated powerhouse app. I have studied Access and 4thDimension yet have always found Filemaker to be much more intuitive, well designed, and easier to get the high-end graphic results desired. Perhaps it has just suited me well, but I think your efforts with the initial learning curve will prove productive. Filemaker lets you display your data in spreadsheet format or, using portals, it is possible to create many complex views of your data. Kevin San Diego, CA

I am using a scripted button to create a new portal record which then takes the user to a specified field in that portal--ready to enter their data. Everthing worked dandy in FM6. (I am working on the newly converted files in FM8.5) I understand the use of a commit record script step and have used it to instantly refresh the portal. However, when the new portal record is created and comitted, up pops a validation error message. The old version (sans commit) put them into the field, let them enter data, and properly triggered the validation when they attempted to leave the record. The new version prematurely triggers the validation through the commit record sript step. I can select "skip data entry validation" on the commit scrpit step, but then the unwitting user will create records with missing data. I have not been able to find any forum entries that discuss auto validation on a portal record. I really like auto validation so I don't have to force my user to hit a "save" button (which I realize could be made to include a post-validation script) --Which I really don't like. Since my portal is sorted, the new portal record must come from a script. I really like how this magically worked in the older version. Is there information I am missing or a workaround? Kevin San Diego, CA