Does anyone know of a method to bypass the message that Alpha sends when a record has been added to a file during an attempted append process?
I have been trying to construct reports in such a way that least impacts other users in our 10 user Novell network.
Within my scripts, up to this point, I have been updating indexes in the primary files of whatever reporting area I'm defining so that I can pass filter parameters to the index I've chosen for the given report. Unfortunately, this heavy index updating has the price of frequent record locking for all users while doing screen adds/edits.
Another method I've tried for reporting involves using a shadow file and building just 1 index for the report in question. This helps by keeping index rebuilding down to a minimum (no dealing with the primary files which have many indexs designed for various purposes).
A third way recently tried was to create a duplicate file for the purpose of temporarily loading it with appended records from the primary file. Once appended, the target set of records is filtered to the report through a custom index. This process creates no record locks at all because the duplicate file has no ties to any active file that users may be add/editing to. The only problem is that if a record is added to the appended file before the append operation is complete, Alpha sends a message over the script announcing the record add which stops the flow of the script. The only thing a user can do at that point is to hit "continue" which breaks them out of the script and puts them back at the custom menu level of the application.
Any ideas of a workaround for this append problem would be appreciated.
I have been trying to construct reports in such a way that least impacts other users in our 10 user Novell network.
Within my scripts, up to this point, I have been updating indexes in the primary files of whatever reporting area I'm defining so that I can pass filter parameters to the index I've chosen for the given report. Unfortunately, this heavy index updating has the price of frequent record locking for all users while doing screen adds/edits.
Another method I've tried for reporting involves using a shadow file and building just 1 index for the report in question. This helps by keeping index rebuilding down to a minimum (no dealing with the primary files which have many indexs designed for various purposes).
A third way recently tried was to create a duplicate file for the purpose of temporarily loading it with appended records from the primary file. Once appended, the target set of records is filtered to the report through a custom index. This process creates no record locks at all because the duplicate file has no ties to any active file that users may be add/editing to. The only problem is that if a record is added to the appended file before the append operation is complete, Alpha sends a message over the script announcing the record add which stops the flow of the script. The only thing a user can do at that point is to hit "continue" which breaks them out of the script and puts them back at the custom menu level of the application.
Any ideas of a workaround for this append problem would be appreciated.