msgbox 'hidden' behind form (1 Viewer)

[SforSoftware]

Hi,

In an Access 2000-database, the messageboxes (called from macro's and vba) sometime (ca 1 on 10 times), apear hidden behind the forms. So that the application seems to be 'frozen'.

We've tried:
- setting popup and modal both to 'No' for the forms
- adding 'systemmodal' to the vbmsgbox-style parameter (instead of applicationmodal)

Both things didn't make any difference

Has anybody seen this problem earlier and found a solution? Any ideas?

Tia,
Bert

 

[KenHigg]

Can you isolate it to a specific series of actions or does it appear entirely random?

kh

 

[SforSoftware]

Hi Ken,

it seems to be entirely random...
it's in before-update-events, (commandbutton)click-events, etc. etc. and in several forms. in 'very old' forms and also in forms that are newly created.

tia,
Bert

 

[KenHigg]

Does it happen on just one pc or does it happen all the pc's?

kh

 

[SforSoftware]

it happens on all the pc's. Three pc's on the customers network (win2k+off2k) and also on my pc (winxp+off2k)

thx,
Bert

 

[KenHigg]

Hum...

I think I would create a new db and start importing stuff small chunks at a time and testing as you until the problem surfaces. That may give you a starting point to trouble shoot.

It sounds like the a form(s) may be trying to continue executing/updating after the message displays and thereby returning the focus back to the form. Could be the app trying to catch up with something on the network?

Hum... Have you tried bringing an entire copy over to a local machine and running it?


kh

 

[SforSoftware]

Importing parts of the application is a way to locate the problem, indeed. but the app is very larche so i'd think that'll take more than a week... (also because the problem occurs 'randomized', so it's not easy to reproduce.

Have you tried bringing an entire copy over to a local machine and running it?

Yes, I did (both front-end and back-end) and that results in the same problem.

It sounds like the a form(s) may be trying to continue executing/updating after the message displays and thereby returning the focus back to the form. Could be the app trying to catch up with something on the network?

That could be. Maybe it's worth trying to give a doevents before calling the msgbox (that's very easy to implement, becease I'm already using a wrapper-function)


When there's nothing else to solve the problem, it's always possible to create a custom msgbox (form), but in my opinion that's not the right way to go

grtz,
Bert

 

[SforSoftware]

ok, I tried the 'doevents', but that didn't help anything.
Then I tried an 'screen.activeform.refresh'. That seems to solve the problem, but that gives problems with validation in beforeupdate-events (the value is saved by the refresh method). the behaviour of the recalc-method is the same as the refresh in this case.

as far as I can see, the problem most times occurs in forms with calculated fields (i.e. a continuous form with two calc.flds in header, one in footer (all dlookups) and one in detail (iif-function), with a few records (ca 5))

Any ideas? It seems to be caused by the calculation of the fields, but how can I work-around it?

tia,
Bert

 

[KenHigg]

What exactly are the message boxes that pop up and lock the sys? Error messages? System or application confirmation type dialog boxes? Custom msgbox's?

kh

 

[SforSoftware]

it are all custom msgboxes, called from macro's or vba.

 

[KenHigg]

Can you disable the calc flds one at a time and/or collectively to see if they may be taxing the sys?

kh

 

[SforSoftware]

thanx, i'll give it a try... (and come back with the results!)

 

[SforSoftware]

Thanx Ken!!
Problem seems to be solved by deleting two calculated fields with dlookup's

grtz,
Bert