Search results

If it wasn't waiting, it would be doing the things that come immediately after submitting the query. It is not doing any of those things, but it does commence doing them as soon as this stupid error message gets dismissed. So I conclude that it is waiting, no matter what you think. Humble...

That seems promising. A pain, as you say, but I'm already showing a different background color - I could just add it to that. But if it's modal, doesn't it stop all other processing as long as it's displayed? And if it's not modal, what is to stop the user from clicking a button under it, unless...

Sorry, you've lost me a bit here. When I filter (I assemble a text string that is submitted to the SQL Server engine via an ODBC link), I get back a recordset, exactly as I would if I were opening a local table, only not so quickly. Yes, it is displayed. A count request is submitted first, to...

Another point, don't know if it's pertinent. The error message does not have the normal debug option. All it has below the error message is an Ok button. When that is clicked, the code continues, and everything works normally, because by that time the query has come back with its results. All I...

I understand asynchronous just fine. What I don't understand is why you think I'm spawning an asynchronous process. I'm not. I'm submitting a query and waiting for the results to come back. That is the exact opposite of an asynchronous process. It doesn't need to know what's going on. It only...

So I would think. But it does, which is the entire reason for this post. I assemble a text string, like "Exec FiltrOrigin.spAkcesity @Poznamka = 'ju'", put it into a pass-through query, and use a normal CurrentDB.OpenRecordset to get the results back. The OpenRecordset command should wait until...

I have NOT disrupted any normal flow. I send a query and wait for the result. I WAIT FOR THE RESULT!!! I am not spawning any process that runs off on its own. If I was, I wouldn't be having this problem, because Access would not be waiting for anything, and could handle the clicks. The whole...

Glad to help. I also had issues with DLookup back when I was first learning Access - I blindly mimicked examples and usually got it to work, but I didn't have a clear understanding of what I was doing. Some people don't like it for speed reasons, but it is very simple and very useful. I usually...

Dlookup has three parameters: 1. The field you want returned from the lookup operation, for instance, you may want to look up the person's last name, using the unique code for a lookup key. In such a case, the first parameter would be "LastName", assuming that is the name of the field in the...

The BeforeUpdate event allows you to set its Cancel parameter, which automatically holds the form's focus in the field, instead of having to use SetFocus in code. Also, it allows you to leave the field with ESC, while using the LostFocus event can trap you in the field, as you pointed out.

In the field's BeforeUpdate event - then you can cancel the update BEFORE it happens, which it sounds like you want. Another way in in the field's Change event - there you can test even one keystroke at a time, if you want, and immediately flash a warning if the entry strays from permitted...

I had a .Requery command, and that seemed to be where the problem was cropping up. At least I think it was. This is a little hard to track, as a built-in construct, a form's native .Recordset property suddenly is non-functional, but it does not throw an error at the point when it BECOMES...

Hm, never thought of defining a separate recordset object. I'll give that a try. Thank you for the idea.

But this is only the declarations of the variables. The actual instantiation, as I have written several times, is in the load event of the main form, so: Set gbl_frmAkces = Me Set gbl_frmPodrobnosti = gbl_frmAkces.sfPodrobnosti.Form If you think this is not correct, what do you suggest I try...

The global variables are declared in a code module: Public gbl_frmAkces As Form_Akces Public gbl_frmPodrobnosti As Form_Podrobnosti This declaration is the only place I use the Form_ syntax.

I do change the underlying recordset, by changing the text of the pass-through query that feeds the subform. I no longer use the Form_ syntax, after an exchange in a different thread, where it was explained to me that it is not the proper way to refer to such things.

I can do that, but I also need to set the current record of the form. Most of this is taking place in a search function. The user specifies a record indentifier, and the DB searches for a record matching that request. When such a record(s) exists, the subform is supposed to display it. Sometimes...

We did, and they are not. This is that same app, but based on that thread, I have replaced all such references with the syntax I now specified here - global object variables, set to the Me reference on form load: Set gbl_frmAkces = Me Set gbl_frmPodrobnosti = gbl_frmAkces.sfPodrobnosti.Form

Thank you, but that is not really possible. This is a client in a client-server app. Constructing local versions of all the tables, making fake procedures to mimic the SQL Server stored procedures and changing everything to use those fakes would be an insane amount of work, with zero guarantee...

Sorry, I meant a specifically declared class module, as well as the built-in class module of the form. I have also tried the Me. variation - same problem. I have done what you suggest - the code stops on the error. I have disabled all error trapping and simply let the code bomb and stop, so I...