VB5 .frm to Access

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

orsteve - 31 May 2007 15:11 GMT

I have an old vb program (form) that I need to edit/update to work with new
hardware. Is it possible to "open" a .frm in the vb editor within Access?
Is there a conversion tool? Migration tool? All of the tools I have seen
are the other way around...

When I try to import a .frm I get the error message "The form class
contained in 'F:\locationdetails...' is not supported in VBE. The file can't
be loaded".

Any help would be very much appreciated.

Thanks,
Steve

Reply to this Message

Arvin Meyer [MVP] - 31 May 2007 15:52 GMT

The form definitions of the 2 products are quite different. Access makes
heavy use of subclassing, where that is merely a small part of VB 6.0 and
almost insignificant in VB 5.0. Code is also different, but not so much so
that it is time consuming to convert. You will however, need a strong
knowledge of both products.

Signature

Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

>I have an old vb program (form) that I need to edit/update to work with new
> hardware. Is it possible to "open" a .frm in the vb editor within Access?
[quoted text clipped - 10 lines]
> Thanks,
> Steve

Reply to this Message

David W. Fenton - 31 May 2007 22:13 GMT

> I have an old vb program (form) that I need to edit/update to work
> with new hardware. Is it possible to "open" a .frm in the vb
[quoted text clipped - 6 lines]
>
> Any help would be very much appreciated.

Try exporting an Access to text (using Application.SaveAsText) form
of more-or-less equal complexity. This will show you which
attributes Access uses. Delete those attributes from the VB form
you're trying to import and then give it a go. I've often imported
VB forms and classes into Access by simply adjusting the header and
removing unsupported functionality form the code.

Signature

David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply to this Message