Access weirdness

[bastien]

I built a subscription application with Access 97. When I delivered it to the client, he was unable to view a set of labels,( gets a #Name? reference error, yet the query which drives the report is fine???) and the application does not exit properly, the .ldb file hangs around and the access framework also does not close.

This application works perfectly on my machine. Access 97 on Windows NT, uses VBA coding for some queries. The mailing labels run off of a query, which does show the correct data in the datasheet view. Even if I rebuild the queries and reports on the client machine, nothing shows. This really confusing, I have recompiled all modules and forms and nothing seems to work.

Any ideas?

TIA

 

[mission2java_78]

Your client maybe missing a .dll. But the main problem could be references. You need to go to your clients machine into the vb code window Tools->references and check for anything that is marked off as MISSING.

Jon

 

[bastien]

That was it

thanks...still doesn't solve the hanging after the docmd.quit but I think that is another install type issue.....

Bastien

 

[mission2java_78]

No Problem...
as for the docmd.quit I know the problem with that too but I need your help in determining the root of it. Where do you call DoCmd.Quit?

Jon

 

[bastien]

well...

I was calling in an extra button inserted on the switchboard, after I had tried just using the switchboard...either resulted in the same problem...

any ideas would be appreciated....

 

[mission2java_78]

Create a small simple 2-minute form.
2 buttons Yes, No

Leave the switchboard as it is with the last item on the switchboard, "Exit System" in the table Switchvoard Items make sure this opens your newly created form, frmExitConfirmation. This form should be a pop up. In the onclick of no:
DoCmd.Close acForm, Me.Name

In the onclick of yes:
DoCmd.Quit

This should resolve any problems.

Jon

 

[bastien]

Thanks Mission

That solved it...just out of curiosity, what causes this to happen?

 

[mission2java_78]

This usually..and I mean usually not always so dont take this as a solution has to do with the order of events. Your switchboard maybe running *other* code and DoCmd.Quit may interrupt this process causing an abnormal quit. You could of gotten away with this using DoEvents..but that isnt generally used much. To avoid these conflicts opening a form and then processing a DoCmd.Quit usually fixes up the problem.
Jon