Tim wrote:
<<Just add a public Boolean member variable (CustomersFound) to your database instance, and then set the variable to False in the BeforeLoad, and then set it accordingly in the AfterLoad.  Or, you could do it way easier and just have the other areas of the application test the RowCount property of the dataset in question.  The functionality is equivalent.>>


Thanks for the pointers. I basically followed this and am able to see one record. About to test to see how this holds up in a loop of several.


<< I sense that what you're looking for is a way to make this process synchronous, which will *not* be possible in a browser environment.>>

Yes. Those times when one has to break away from the conditioned desktop app process can be quite trying until one gets the hang of it.

<< Yes. Those times when one has to break away from the conditioned desktop app process can be quite trying until one gets the hang of it. >>

Well, it's a shame that the browser vendors can't understand the value of synchronous execution in certain contexts, regardless of their concerns regarding the unresponsiveness that can be associated with "waiting".  There's nothing to stop them from offering a way to execute a server request in a background thread and have the JS engine stop to wait for a response, while still allowing the main UI thread in the browser to respond to Windows messages so that Windows doesn't think the application is unresponsive.  In fact, that is exactly how the synchronous AJAX requests worked, but they've since been deprecated and are not recommended for usage, which is why EWB doesn't use them.  Now we have to wait until all commonly-used browsers support "await" operations....

Tim Young
Elevate Software
www.elevatesoft.com