It hasn't crashed yet using the web client, but it's only a matter of time. (The problem didn't go away, but it should reoccur on one of the two machines.)
Has it crashed yet? This is a fairly crucial test.
The one problem we noticed with the web client was that if you open up a Foundation process (to a certain table), the process is named after the last graphic that was loaded by our Active4D home page: "/Graphics/BuiltWithOSX.GIF". (I double-checked this by calling a simple wrapper method which retrieves the name of a process given the process number.) The corresponding process on the server is named "•Project" as it should be. (?????) I think at the time, we had both the 4D Server's web server and the web client's web server running at the same time. This shouldn't have been a problem though, should it?
I think this is just 4D reusing a dead web process and not updating the name correctly on the client side.
Bart Alcorn <[EMAIL PROTECTED]> is having very similar problems. (He also has Active4D) Here was his comment to me:
One episode yesterday, crashed, then crashed twice again immediately upon restarting, and then smooth sailing so far. Very typical.
If it is crashing _immediately_ upon restarting, it's hard to see how this is related to Active4D...
This is exactly what's happening to us.
I have a client who has had random freezes, but they have now isolated it to 4D itself. It seems to have something to do with triggers.
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
"If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoylibrary.com
