Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

VB6 References Not Working

  • 18-07-2006 12:37pm
    #1
    JuncoPartner
    Closed Accounts Posts: 161 ✭✭


    Hi, maybe someone will have a better idea than me what's going on here.
    I'm in the process of moving all of my projects off an old machine and onto a new one.
    I have a project group containing 8 or 9 projects.
    When I try to compile or run I get the User-defined type not defined error. The class it is complaining about is in one of my other projects in the group.
    So going into references the project reference is already ticked. I need to uncheck it, try to compile. Then check it again and the compile works. This happens every time I open the project group for all of my references. I need to uncheck them all, try compile and recheck them.
    When I open the projects on their own the references are instead pointing to compiled dlls of my other projects and everything compiles ok.
    Anybody got any ideas?
    It only seems to be happening with the one project group, all of my other VB6 apps are working fine.


Comments

  • #2
    amen
    Registered Users, Registered Users 2 Posts: 2,781 ✭✭✭amen


    I think you have a problem with the Binary Compatability option in VB.

    In vb Binary Compatability is set to off by default so when you recompile a dll its GUID changes everytime so your references are getting screwed up.
    I locate the first project and build it.
    Rename the dll to .cmp.
    Open Vb set the compatibility to binary and point to the .cmp file
    build the dll.
    This should ensure that your GUID doesn't change.
    Repeat for all projects


Advertisement