CDML & duplicating records

[burnsy]

I need your help!

Using CDML, a web-user can create a new record in the database. On submit, a script is run that finds all the records in the database that particular user has created and using a loop, edits each record in a certain way.

My question is...while this looping, going to the next record and field modification is going on...if a different user visits the site, runs the script, could there be any mixups between the two users doing things simultaneously?

Thanks!

[rdhaden]

Oh no, here it comes again...

[Garry Claridge]

Yes, they will clash!

Check Keith's solution at http://www.simplifyfm.com:591/

Or

Take Anatoli's advice and don't use them.

Good Luck

Garry

[Anatoli]

I am quiet...

[ibiubu]

PLEASE FileMaker...how long must we plead before you add multi-thread capabilities to web companion for scripts. Dont keep pushing scriptmaker as being compatible with web companion.

LR

[Anatoli]

Not very practical request:

a) First user has found set of 10000 records and it is replacing something in them with script.

Second user has another found set of 10000 records and it is replacing something completely in them with another script.

Now tell me, even if the scripts can run concurrently, how will SINGLE UNLIMITED (basically single client) handle this? Jumping between found sets?

What if another user will need another found set for sort and display?

[Keith M. Davie]

"My question is...while this looping, going to the next record and field modification is going on...if a different user visits the site, runs the script, could there be any mixups between the two users doing things simultaneously"

First off. looping scripts are a very bad idea in web publishing.

Second, to find out why, try some testing of what you are doing. It is simple. Open three browser windows. Get to the page whene your looping script is invoked on two of those browser windows. Invoke the script in one, then double-click (activate browser and submit request) in the second, then go to the third and try to assess your home page as if a new client were trying to access your site.

And don't let the running of the second script fool you. That happens with a looping script. For some reason a looping script will somehow allow a second event to be queued. At least that is the case with FMPro 4.0 and 5.0. In all other scripts (including 5.5 and 6.0) the second event just does not perform and is not queued.

[Garry Claridge]

RE: Now tell me, even if the scripts can run concurrently, how will SINGLE UNLIMITED (basically single client) handle this? Jumping between found sets?

The same as other multi-user, multi-threaded Database Managment Systems!

Garry

[Anatoli]

Yeah, but the original question was just:

PLEASE FileMaker...how long must we plead before you add multi-thread capabilities to web companion for scripts. Dont keep pushing scriptmaker as being compatible with web companion.

There is not request for more multithreading, just for the scripts. What I was pointing out was the FULL multithread answer. And that is another ball game, isn't it?

And yes, I love to see that, but IMHO if that will ever occur I'll be already retired.

[Garry Claridge]

RE: multithreading, just for the scripts. What I was pointing out was the FULL multithread answer

Good point. If the price doesn't go up accordingly, they will have a killer app!

Garry

[Anatoli]

Sure.

We need that especially for web. And if the price is twice the price of Current Unlimited, almost everyone will pay that.

If it is higher, we can all use WSC and RAIC.

Is the WSC really watching the status of Unlimited? Like if it is busy, go to another machine? Like serving, 1-1-1-2-1-1-2-3-2-2-3-1-1 ... you get the idea!

Or is it just the sequence 1-2-3-1-2-3-1-2-3? In this case it will be still knocking the scripts if they are longer...