Results 1 to 9 of 9
  1. #1
    Join Date
    Nov 2002
    Location
    Hamburg, Germany
    Posts
    14

    Unhappy Unanswered: Strange behaviour when running app on different machine

    Hi all,

    I'm experiencing a strange problem when trying to run my access application on a different machine.

    The VBA code runs fine until it hits the following command:
    Set UserTable = CurrentDb().OpenRecordset("User", dbOpenDynaset)

    I then get runtime error 429. I'm running the german version of access so I can't give you the exact english error description but it's something like "Object creation through activex component not possible"

    Has anybody got any suggestions?

    Thanks a lot,
    Ulf Moehring

  2. #2
    Join Date
    Jul 2003
    Posts
    38
    Hello Ulf!

    You should also post the context of the command, i.e. is it run from a activeX?
    The correct Syntax is btw Currentdb.Openrecordset, and you should replace CurrentDB by a DAO.database variable:

    dim db as DAO.database
    set db=currentdb
    set UserTable=db.Openrecordset("User",dbOpenDynaset)

    Maybe this is the solution, otherwise please post a further explaination

    regards

  3. #3
    Join Date
    May 2003
    Location
    Dallas
    Posts
    817
    Provided Answers: 5
    depending on the version of access you may have a referencing error

    if yoiu are using DAO and creating this code in 2000 or XP then access will default to the ADO library, hence giving this type of error.

    goto the VB window and click tools / references

    3rd to 4th option down will show if ADO or DAO is loaded

    if both are present and you want to use dao like you have in other apps - you may have to set the priority of the DAO library above that of ADO

    If you are not going to use the ADO - uncheck it.

  4. #4
    Join Date
    Nov 2002
    Location
    Hamburg, Germany
    Posts
    14
    Hmm. I checked the reference entries - everything seems fine.

    I even skipped the "Set UserTable..." command but that just caused the error to appear when executing another line. So I really don't think my code is the problem here...

    I'll check again if every ocx file needed is where it should be...

    Thanks for your help though! If anybody has any other suggestions please post them...

  5. #5
    Join Date
    Nov 2002
    Location
    Hamburg, Germany
    Posts
    14
    All files are where they are supposed to be. I really don't know what to check next...

  6. #6
    Join Date
    Nov 2002
    Location
    Hamburg, Germany
    Posts
    14
    I checked my code again and it seems that the error occurs every time I use the CurrentDb() function like in "Set db = CurrentDb"

    Has anybody got any further suggestions like how to replace that statement?

  7. #7
    Join Date
    Jul 2003
    Posts
    38
    Hey ulf, the problem you are encountering comes from an ocx without the correct license. I guess it's comdlg32.ocx ...

    There is a patch for it on the Microsoft homepage, look for VB6CLI.exe.

    regards

  8. #8
    Join Date
    Nov 2002
    Location
    Hamburg, Germany
    Posts
    14
    Hmm, I'm a bit confused now. I don't have any version of visual basic installed on both systems (at least that's what the VBC6 installer tells me...). Apparently I don't need it either as the access application runs fine on the machine I developed it on...

    Can I obtain an activex control package anywhere containing the comdlg32.ocx?

    Please help me! I'm really confused right now!

  9. #9
    Join Date
    Jul 2003
    Posts
    38
    This ActiveX isn't used only in VB6, but also in the ODE-Tools, for example.
    You can obtain a license patch for these ActiveX controls from Microsoft, as i said; but you need to know where you got this ActiveX's from, or install VB6 and then install the patch you already have.

    Other suggestion: did you use >> dim db as DAO.database << ?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •