Access 2003 program with runtime version using 2007 and....

[Damon Heron]

it seems to run okay on WinXP. I have a friend that has Vista. I gave him
the runtime version, and all worked fine with the exception of one form.
Vista came back with a msg that "Access has stopped working" and "close the
program". I looked at that form to see if there was anything unusual about
it, and found that I had inadvertantly left an activeX "ctreeview" control
on the form. This control has no code, it was just a goof on my part to
leave it on the form. My question is, until I can get my friend (who lives
in another state) an updated version, can anyone duplicate this behaviour?
It has to be Vista, because XP has no problem with it.

TIA
Damon

 

[Klatuu]

Most likey it is not a Vist issue. I would suspect your friend does not have
the Active X control installed or registered on his computer. There are two
solutions. Remove the control from the form, recreate your mde and send it
to him. The other would be to have him install the ActiveX control on his
computer and register it. The issue here, however, is licensing. Most
ActiveX controls require a use license. You would have to check with the
vendor of the control to determine if it can be distributed.

 

[Tony Toews [MVP]]

Remove the control from the form, recreate your mde and send it
to him.

Also ensure it isn't left behind in the references in the VBA editor.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Klatuu]

Good point, Tony.
Also, come to think about it, could the OP be using Early Binding and
creating a version difference issue. I know we had that big time going from
2000 to 2003.

 

[Damon Heron]

I am using late binding on all my code.
I believe the problem was a reference issue and will know for sure in a day
or so when my friend does some testing and reports back to me. I will post
more when I find out.

Damon

 

[Tony Toews [MVP]]

Also, come to think about it, could the OP be using Early Binding and
creating a version difference issue. I know we had that big time going from
2000 to 2003.

That could be. I'm not familiar with the symptoms of dealing with
different OCX versions.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Damon Heron]

It was the ctreeview control. Once I removed it and gave him a new copy,
all was working well on Vista. However, I still don't know why it would
work on various PCs running XP and not the one PC that had Vista.

Damon

 

[Tony Toews [MVP]]

It was the ctreeview control. Once I removed it and gave him a new copy,
all was working well on Vista. However, I still don't know why it would
work on various PCs running XP and not the one PC that had Vista.

Some other software installed on those systems which isn't installed
on the Vista system could have installed that control.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/