Developing solutions using the Trasactional data entry model

[Jalz]

Hi Guys,

Ive finally migrated my FP5 solution to the new FP7 format, and boy its been great learning the new language and the potential power of FMP 8.

Im going to be embarking on a new project and I'd like to use the "transactional" method of data entry, i.e. use a save/submit button which will be scripted to commit records once the user has finished editing or adding a record.

My question is, has anyone used this method successfully, and what kind of pitfalls should I look at out for? I've always disliked the fact that anyone could edit records easily without even knowing. Im concerned about editing portals and records mainly in a multiuser environment....

I'd love to hear if any of you guys have adopted this approach.

[Zero Tolerence]

Make sure they can't edit records in portals, just shut data entry off in browse mode I always use transactional methods for data.

The only time I let a user create a new record is by clicking a button. Then, if they don't click "Done" or "Save" I delete the record.

A few tips for you:

1. Learn to use Pause Script to make sure your users can't abort a transaction.

2. On your done/save button script, check for valid data.

The idea here, is to make the user not be able to do anything, unless you give them a button to do it.

[Jalz]

Hi Zero Tolerance,

Thankyou for your reply. I think I'll create a very simple file so I can get my head around the concept and try putting in some of the logic you've just stated

.

How long have you used the transactional model? and have you had many conflicts with network users, without committing a record - I guess the records are open, how does FM cope?

Jalz

[Zero Tolerence]

Perhaps you should look into having your users enter the data into global fields, and then if its valid data, add a record to the actual data.

[Jalz]

I think I will try and attempt for my application to mimic the behaviour if your first post. I can see the use of global fields for portals being ok (I've seen this in FileMaker Business Tracker) - but I would rather get the users to alter teh "real" fields and commit if the data is correct.

[Jalz]

Guys,

I've been prototyping a very simple file with the transactional method of data entry - before I convert my entire solution to use this method.

I've attached a very simple sample file, which allows me to create / edit the master record and then either revert/or save the changes. The problem at the moment is in the edit script, I've used the Pause/resume script, so that when I'm editing the record, the Window that allows me to edit the record behaves like a modal window until the user saves or cancels.

When I click on save, my script continues, and the pause/resume dissapears, but when the actual edit window closes, the pause/resume step kicks back in the main window. Does anyone know how I can prevent the script from pausing in the main window(apart from using the halt script)?

Finally, any ideas the best method to create transactional data entry for a portal?

Thanks in advance

Jalz

Transactional_Test.zip

Edited October 17, 2005 by Guest

[Jalz]

Guys,

I've finally decided upon the set of scripts I'm going to use for my data entry, and I've attached a very simple sample file, with one field and four scripts : New, Edit, Save and Cancel. Can any of you guys who produce solutions using this method for data entry and editing, give my file a once over and tell me if the scripts should work ok in a multiuser environment.

Cheers.

Jalz

TestDataEntry.zip

Edited October 18, 2005 by Guest
New file attached with a portal