Search results

Pretty neat. Unforeseen and unintended consequences are a regular occurrence in all sorts of complex systems. Software is no exception. Part of what makes the field challenging, I guess.

I've run into a weird one. I have a form that had NO controls that could take focus. All was controlled from the ribbon, and the form only displayed things in response to procedures called from the ribbon. Recently, I tried an experiment, and add a few controls to the form. They work, but when I...

"Waiting and doing nothing..." Waiting for what? The sun to go down? If you are waiting, then you are waiting for the other process. THAT makes it synchronous. There is always the option to not wait, but if you need the results from the partner process, not waiting is silly. What would you do in...

Yes, theoretically it could. But the point is that it doesn't - it waits. In all these cases, Access waits for a response. Sometimes the response is, "Here you go." Sometimes the response is, "Here is the first record, I'm working on the others." In both cases, Access waits for that response...

A ways down the road now, but for the sake of completeness in the archives... I ran across this just recently: https://nolongerset.com/raising-custom-events-in-vba/ The author writes his tutorial much more in line with my understanding of how events are supposed to work, Specifically, he...

The same is true of SQL Server. If I issue a command to execute a stored procedure, the result is available as soon as the procedure completes. That has nothing to do with opening a recordset.

It does NOT. Try it yourself - populate a large local table, then issue an OpenRecordset command and immediately test RecordCount. It will NOT show the full count. It will always be at least one, and in the background, Jet will continue filling in the records, EXACTLY as does SQL Server. If the...

Then you are obviously doing far different sorts of work than what I'm doing. Bound forms are fine for simple manipulations of datasets, but there are a great many tasks that are not nearly so simple. Unbound forms are just another tool in the toolbox. They are good for some things, not good for...

Then why does it not respond to them once processing resumes AFTER the SQL request? It's not queueing them up, and I don't have an asynchronous process. I have repeated this until I am blue in the face. This is something Access is doing on the side, on its own. It does NOT process the clicks...

That's what the yellow color was supposed to do, and what my added disabled events do now. But a DoEvents has nothing to do with that. When I issue an OpenRecordset command, the VBA routine issuing that command STOPS AND WAITS until the server responds. Even if I had the DoEvents immediately...

See #66.

DoEvents releases the processor to allow OTHER tasks to run. It does not allow Access to start another internal thread. I do not think Access has the ability to do this at all. Normally the background is green. I change it to yellow just before initiating communication with the server, and...

I thought so initially, but that is not what is happening, hence this thread. If you read the entire thread, you will see in the discussion that I have written, many times, that my code IS HALTED, waiting for a response from SQL Server to begin filling the requested recordset. It is during this...

I don't see that. EVERY process that communicates with another process has the option of waiting for a response or not. There is no such thing as not having the option of waiting. There is of course specific software that does or does not wait, and the user of that software is limited to what...

But I'm NOT starting an asynchronous process. I'm submitting a query and waiting for the response. I think Access should queue up whatever happens while I'm waiting.

It's all fine to tell me it's my own fault, but it's not very helpful. I assemble a text string, send it off to the SQL Server engine, and wait for a response. There is a timeout parameter in pass-through queries exactly for queries that take a long time, and I am nowhere near hitting that. It...

Bound forms are fine when doing simple things. This app is decidedly NOT simple, and many of its functions would be completely impossible with bound forms. Some can be bound, and are. The more complex ones are out of the question. Saying I 'have to know' how long a query will take is silly. I...

It's not one form, it's pretty much all the forms, and it's kind of random. Sometimes it happens, sometimes it doesn't. I can make it happen pretty reliably by clicking on a button that starts a lengthy task, like getting something complicated from the linked SQL Server database. If I click...

I have a database that is slow to perform some functions. When the users click a button before the task is finished, an error message pops up, saying something like, "Setting of macro or function to property Before Update or Field Validation Rule prevents Microsoft Access from saving data in...

Sorry, I also do not know how to respond to a tautology. But thank you for the demo. It works as you say, of course. I also tried to create my own demo to isolate and reproduce the behavior I am seeing, and was unsuccessful. In my very limited test case, the incorrect behavior also does not...