Object or class does not support the set of events??

[mejia.j88]

hello all,

i have created this very simple to use DB that prints out the information you put in.

i get the following message, which is attached. this is happening for both the "Print and Exit" button as well as the "exit without printing".

the code that runs is:


Option Compare Database

Private Sub txt_print_click()
RunCommand acCmdSaveRecord
Call PrintLabels
DoCmd.Close acForm, Me.Name


End Sub

Private Sub txt_exit_click()
Me.Undo
DoCmd.Close acForm, Me.Name
End Sub

The strange thing is that if i close the form, and reopen it again from the switchboard is that it works (sometimes).

not sure what is happening here, any help/suggestions would help.

thank you.

[aytee111]

Sometimes I find that if I add the VB Extensibility reference then things start working. I don't know enough about any of it to know it this is your problem or not. In the VBA editor, go to Tools and References and add that one - can't remember what it is called exactly.

[ajetrumpet]

Sometimes I find that if I add the VB Extensibility reference then things start working.

this has absolutely nothing to do with it. The primary purpose, as far as I know, of the extensibility DLL is to be able to manipulate a VB project and its dependencies by the actual code that's IN the project.

mejia,

accept for your PrintLabels() procedure, which you did not post, nothing is wrong with your other code.

And to discern anything from the symptoms you're mentioning here, it would be impossible to do for a number of reasons.

But YES, basic has some serious problems associated with it, namely the extreme inconsistent nature of its execution, especially when interfacing with other applications. The variables to these issues are endless, as they always are with MS technology.

The only reasonable solution to decrease the stress of dealing with MS client-based software is to do one of 2 things, IMO:

1) Migrate to IIS and any other server-side interfacing MS language.
2) Ditch MS technology all-together.

[mejia.j88]

yeah i didn't think so either, i've put other DB's together in a similar fashion. PrintLabels i use is several DBs and still works great.

can't quite put my finger on this quirk.

[mejia.j88]

not sure if this might help answer my question but,

on my switchboard i have two buttons, Enter record, and Browse recrods.

browse records has no problems what so ever, and works great, (in fact, it's an exact copy of Enter record except it doesnt save records to the DB, only use is for browsing and printing old records).

if i click Enter Record, then hit the save and print record, the error i posted earlier appears.
upon closing this form, and going to the browse records, then back to the Enter record form, it works great after that.

strange?

[mejia.j88]

as silly as this may seem,
i just tabbed my code over after Private Sub, on both of the event procedures and it worked.

MSAccess is a mystery.