Mscomctl.ocx in runtime app

[Veggis]

Hi

I have a large access application, it registers information on
funerals. And this is sold on as runtime apps to other customers. One
of my customers got new pcs recently, and now certain errors occured -
i.e. the time() function doesn't work. I think the problem is with the
ocx-file, even though the customer has the correct version and all.

I can provoke the error on my machine by copying the application (mdb-
file) to another computer, then the same errors occur, the errors are
for instance that the time() function won't work, also problems with
the format-function. I guess it's part of the mscomctl.ocx library.
What I need to do on my machine to get it to work is unregister the
file in references (visual basic - unhook and click ok), then go in
again and browse, select the same file so it gets added under
references again. Now everything works fine.

But I can't do the same at the customer, because he has the runtime
app without access. Any ideas what is wrong and how I can fix it? I've
developed it in access 2003, using VB6.3. I've tried unregister the
file with regsvr32.ocx, then register it again, but that doesn't work.
And I've tried using the old comctl32.ocx-file.

thank you

Vegard

[Tom van Stiphout]

On Sat, 02 Jun 2007 06:31:40 -0700, Veggis <ve******@gmail.comwrote:

Your symptoms are classic broken reference. See
http://www.mvps.org/access/bugs/bugs0001.htm, and bookmark that site.

Don't guess. At startup time iterate over the References collection,
looking for IsBroken. Use fully qualified function names (e.g.
VBA.Left$ rather than Left$) so your code will work even if there is a
broken reference. Then report which one is missing, and exit
application.

-Tom.

>Hi

I have a large access application, it registers information on
funerals. And this is sold on as runtime apps to other customers. One
of my customers got new pcs recently, and now certain errors occured -
i.e. the time() function doesn't work. I think the problem is with the
ocx-file, even though the customer has the correct version and all.

I can provoke the error on my machine by copying the application (mdb-
file) to another computer, then the same errors occur, the errors are
for instance that the time() function won't work, also problems with
the format-function. I guess it's part of the mscomctl.ocx library.
What I need to do on my machine to get it to work is unregister the
file in references (visual basic - unhook and click ok), then go in
again and browse, select the same file so it gets added under
references again. Now everything works fine.

But I can't do the same at the customer, because he has the runtime
app without access. Any ideas what is wrong and how I can fix it? I've
developed it in access 2003, using VB6.3. I've tried unregister the
file with regsvr32.ocx, then register it again, but that doesn't work.
And I've tried using the old comctl32.ocx-file.

thank you

Vegard

[Veggis]

I will try that. Thanks a lot for the effort!
On 2 Jun, 22:34, Tom van Stiphout <[e-mail]:

On Sat, 02 Jun 2007 06:31:40 -0700, Veggis <[e-mail]:

Your symptoms are classic broken reference. Seehttp://www.mvps.org/access/bugs/bugs0001.htm, and bookmark that site.

Don't guess. At startup time iterate over the References collection,
looking for IsBroken. Use fully qualified function names (e.g.
VBA.Left$ rather than Left$) so your code will work even if there is a
broken reference. Then report which one is missing, and exit
application.

-Tom.

Hi

I have a large access application, it registers information on
funerals. And this is sold on as runtime apps to other customers. One
of my customers got new pcs recently, and now certain errors occured -
i.e. the time() function doesn't work. I think the problem is with the
ocx-file, even though the customer has the correct version and all.

I can provoke the error on my machine by copying the application (mdb-
file) to another computer, then the same errors occur, the errors are
for instance that the time() function won't work, also problems with
the format-function. I guess it's part of the mscomctl.ocx library.
What I need to do on my machine to get it to work is unregister the
file in references (visual basic - unhook and click ok), then go in
again and browse, select the same file so it gets added under
references again. Now everything works fine.

But I can't do the same at the customer, because he has the runtime
app without access. Any ideas what is wrong and how I can fix it? I've
developed it in access 2003, using VB6.3. I've tried unregister the
file with regsvr32.ocx, then register it again, but that doesn't work.
And I've tried using the old comctl32.ocx-file.

thank you

Vegard