forum home | register | profile | members |search | faq
homepage | lost password? | chat room
|
|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > Changes to Specification > Apple Events and Deleting Records | You are not logged in. Login or Register. |
| Pages: 1 |
|
| Author: | Topic: Apple Events and Deleting Records | |||
Matt Posts: 107 Registered: 2003-02-16  mstrange@mac.com  |
 Posted: Jul 04, 2004 7:37:16 pm    
Error 250 (Tried to delete a records that is write locked) has always been in the list. However, prior to Helix 5, Helix just deleted the record anyhow. That was fixed in Helix 5. Now, however, when a record is write locked, Helix just replies with a 0 in the "number of records deleted" field (nDeleted in the original spec), and the 250 error is not generated. The question is whether we want to investigate getting it working as per the original spec, or revise the spec to align with the current reality. (Either way, the same net effect is realized.)
|
|||
Fred Posts: 57 Registered: 2003-04-10 |
Posted: Jul 05, 2004 9:34:47 am
Matt, are you saying that if I do a batch delete and the record that is locked is the ninth in the batch then I'll get a "0 record deleted reply" ? If so then have the first eight been deleted? If that is the case then I would like it as per spec. Fred |
|||
| Matt Posts: 107 Registered: 2003-02-16 mstrange@mac.com |
Posted: Jul 05, 2004 10:09:33 am
No, my example refers to a single record delete. Currently Helix would (in your example) return a 7 and no error, even though the original spec indicates it should return a 250 (write lock) error along with the 7. nDeleted tells you how many records were deleted, errNum tells you what error is encountered. Applescript has a rarely used 'partial reply' attribute that is returned 'on error' so it must be technically possible to return nDeleted and generate errNum 250 at the same time. The original AEEA spec says Helix returns nDeleted when a record could not be deleted, so errNum 250 seems to be left out in the cold. The question is whether or not to investigate and find out whether this is by design or by accident. - Edited by Matt on: Jul 05, 2004 10:25:21 am
|
|||
| Fred Posts: 57 Registered: 2003-04-10 |
Posted: Jul 05, 2004 10:45:44 am
Ok. I check the returned number against the AEdesclist count -1 in my AE. So am I right in assuming that if the counts do not compare then it is solely due to a write lock? Fred |
|||
| Matt Posts: 107 Registered: 2003-02-16 mstrange@mac.com |
Posted: Jul 05, 2004 11:06:55 am
No, you can only assume Helix would not delete it for some reason. Technically, you have no idea why it didn't delete.
|
|||
| Fred Posts: 57 Registered: 2003-04-10 |
Posted: Jul 05, 2004 12:13:21 pm
Fine. In that case I would like the errnum. So to answer you initial question : yes please investigate and get it to work as per spec. That way we'll have one less error to hunt for. Fred |
|||
| Fred Posts: 57 Registered: 2003-04-10 |
Posted: Jul 05, 2004 12:16:39 pm
Matt, It would also be nice to know who was locking the record 
|
| Pages: 1 |
|
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |
