Thanks for the feedback, everyone.
I agree that .Init and .Kill will cause problems when run from a FORM. I mentioned that in the article when doing an example of a button on the form. You only use this when using standalone code, which I was calling from the Menu, not a form which is already using the table in question.
I wasn’t aware of the other SET option, which I will check out.
The help file says that .UseFile should be used before the file is opened.
The UseFile method notifies ABC Library objects that the managed file whose opening was delayed by the LazyOpen property is about to be used. UseFile returns a value indicating whether the file is ready for use. A return value of Level:Benign indicates the file is ready; any other return value indicates a problem. UseFile should always be called before a file is opened.
I added a button to the Customer browse, and used an action to call the standalone procedure as a new thread. I didn’t get any errors or exceptions in debug mode. maybe because it was a separate thread?
Brent Ozar is brilliant. He wrote a series of tests you can run on MSSQL Server to make sure it is running well. Saved me a lot of trouble.