by James Bott » Fri Oct 16, 2009 11:42 am
Richard,
That looks like a nice workaround but it looks like the user is going to be quite surprised when the browse just automatically closes on them.
Here is how you can track down where the database is being closed. Create a transaction log file and record when each function of the buttons is being called and also when your workaround is being called. Then after a few days or a week you can look at the log file and see exactly were the workaround was called. The function immediately previous to that is where the database is being closed. Then you will know where to search.
James