Posted by Robert G Laurin on August 14, 2012 at 09:03:30:
The new Error popup in Comet 32 is, in my humble opinion, totally useless....
Could Comet be more friendly with the errors? Giving a cryptic error window with no valuable information is a step backward.
In the Comet16 Days, people (end-users) had the good habit of doing a Print Screen of the error before they ran for help. Now I have to try to find the information in the new error-log, which is now on directory COS that most users don't have access to anyway. I keep COS for the XAP junk folder.
With the 32 bits there, can PSTAT be properly populated upon action (or at least on EXCP/EXCPSUB). Better yet, can a set of new system variables be created for reporting on last error? Comet is the only system where information on last error is kept from the programmer. Can we take another step forward?
Please!
PS: I already have a built-in error-trap function, wrote it 15 years ago, never worked because PSTAT if oblivious of the last Comet activities.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.