May 11, 200520 yr Hello Jalz, You may or may not need a commit step in a script such as the one you have cited. It depends entirely on what it is you are trying to achieve. If you simply want the script to set the record up and hand it over to the user, then the script will likely be fine without a commit - the user can do that once they have finished with the record. It would be only if you need to build indexes for the record or to establish links to other records that you might consider committing the record prior to end-user data entry.
May 11, 200520 yr Author Thanks Ray, That makes sense now. I've just converted my FP5 files to 7, and ran a couple of simple scripts like the new record script illustrated in my first post from my converted solution. The script seems to run fine in single user mode, however in multi-user environment, the second clients machine keeps saying the client 1 in modifying record....hence the question. I thought I was going to have to edit ALL scripts with setfield command, but from your explanation, only the ones where the user wont have any data entry fields available in my solution.
Create an account or sign in to comment