Search results

No sweat, old does not mean dead. Sometimes useful insights come long after the original matter has been resolved, and those may be useful for future issues, or useful to someone else with a similar problem, browsing the archives for information. Many of my projects contain one main table and...

I finally settled on a fairly simple adaptation. In the code that shows the warning yellow background, indicating that the app is waiting for records to start coming back from the server, I added the following: With gbl_frmAkces .AllowEdits = False .AllowDeletions = False...

Yes, I MoveLast as well. I've used ADO very rarely - I remember it has that ability, but I don't recall ever using it. Most of my stuff is small enough that I don't need to stage stuff that way.

Um, yes - that's what I've been saying all along. What I got from you and others, like Pat Hartman, was that Access issues the OpenRecordset command and IMMEDIATELY continues, without waiting for any sort of response - an asynchronous process - a process spawned and left to its own devices, with...

I'm not at work now - shop is closed for the holiday. I can't try anything more until I get back to work, but I have thanked those who provided a testable suggestion, and have made notes of what I intend to try. And I'm only disputing things I know from my own experience - specifically the...

NO, it's not. I've tested this many times. Both SQL Server and Jet respond with the first record requested record and not before. SQL Server does NOT respond with a message saying, "Okay, I'll get to work on that." It responds with the recordset. Sometimes with just the beginning and gradually...

AND he's wrong. As I've written here repeatedly, the code after the query call does NOT execute until AFTER the server responds. Access waits for the DB engine's response.

Not in my experience. Even with local Jet, if I open a large recordset, checking the record count immediately after the OpenRecordset command, the count is less than the total. Repeatedly checking the count shows that it gradually increases. The only way to make sure you have all the records is...

I have run into this with records in a BE that do not have a unique identifier. It's a very misleading error message, but the gist is that there is no reliable way to identify the record being delivered by the FE to the BE without such an identifier, so the BE refuses to accept it. No idea why...

Well - yes. That is what makes it NOT asynchronous - I'm waiting. An asynchronous process would be one that I send off and then continue on to do something else. I don't, and in fact, I don't even know how I would do that. I'm sure I could find out with a bit of digging (a property in the...

Not quite - as Pat pointed out a few posts back (and I had spaced over when I wrote my own objection to it), a modal form halts all execution OTHER THAN in the modal form. The modal form blocks all other user activity, but its own code continues to run. It can make the query call, and wait...

Not at all a stupid question. That would work to block clicks, but the problem with a progress meter is that I have no way of knowing how far along SQL Server is in the job. These are pass-through queries - I build them, submit them and wait for the results to come back. They generally come back...

And now that I think about it, I wonder if I could just disable the entire form, and that would cover everything in one command. I'm not at work for a few days now, but I have several things to test when I get back. This is going to be interesting.

Thanks - yes, that would work. I would have to make it a bit more complicated, because I have toggles, embedded subform and other things on the form, and some of them are already disabled for various reasons, so I would have to keep track of every control's status before calling this routine and...

I could, but there are MANY buttons on the form, as well as a bound subform, also with buttons. Constantly disabling and re-enabling everything would be a monumental PIA, as well as probably making the form flicker a lot. I'm trying to avoid that.

That would make sense as to what is happening. I don't think it's the full explanation, because for instance, you can't interrupt a stuck loop with a mouse click on the VBA Stop execution button, unless you have a DoEvents line somewhere in the loop. So some mouse clicks get ignored, although...

Many things seem weird to people who don't understand them. But that's okay, I'm not trying to educate the world, just solve my own little problem. I don't know how to respond to meaningless tautologies. And I have said from the start that I do not have such a process, unless you consider a...

Oh, right. I wasn't thinking clearly about that. I think you might have known, since there was no mention of anything like that until you brought it up to brag about how you had large clients, while constantly insisting that I was doing something which I most definitely am not - spawning an...

You mean like a mask, that would keep them from be able to touch anything, but would not mangle the display? That's an intriguing idea - thank you. Never done anything like that, but it sounds very much worth trying. I'll give it a shot and see how it works.

That's how I understand modal forms as well. But if it stops all Access activity, how does Access then submit the query? All my modal forms work that way - everything stops until the user deals with the modal form. I pop up a modal form and the app will sit, waiting for the user to do something...