compatibility problem Win7

  • Hello,

    I have problem to run ms access application (.adp) under Win7

    with MS office 2007.(or access runtime 2007)

    Database is placed on SQL2000 server.

    When I want to open some form, the same error message appier.

    (see attachment)

    Thank you.

  • Can you set a breakpoint in your OnLoad event and step through to see what line is causing problems?

  • Yes I have set up breakpoint, but I could not get to this point , always the first was mentioned error message. I dont have this problem with WinXP, everything works fine. I was testing the setting with SQL server2000, If the connection is okay, I got successfull response.

    When I create completely new form, and set event procedure, then everything works fine.But I have a lot forms where is set event procedure.I dont use macro.

  • Exactly what do you have in the expression for the OnLoad event on the form? The error message you are getting indicates that it can't find anything in the VBA project that matches what you have in the property for the OnLoad event. This could be coming from a missing reference in your VBA project. Also, have you tested it with a later version of SQL Server? The OLE-DB driver for SQL Server in Win-7 is quite different from what you have in Win-XP.

    Wendell
    Colorful Colorado
    You can't see the view if you don't climb the mountain!

  • It doesn' t matter what is in expression, because this error appier always, I want to open a form.

    1. If I delete OnLoad event in origin form then the form is opened without error message.

    2. If I add OnLoad event to origin form for example: Msgbox "hallo" ...I got error message.

    3. If I create completely new form it works fine.

    No I didnt tested it with later version of sql server. Do you think that problem is in version sql?

    btw...SQL2000 db server is installed on system W2003 server.

  • Which version of Windows 7 do you have? Have you tried to run a debug on your code? What kind of controls do you use on that form? Have you checked the REFERENCES in the VBA IDE?

  • So what exactly do you want to happen with the OnLoad event on the form? Apparently it is working just fine on Win-XP, but not on Win-7. The OnLoad event must either contain the name of a macro, a VBA procedure, or an expression (which is rarely used ).

    Wendell
    Colorful Colorado
    You can't see the view if you don't climb the mountain!

  • Which version of Windows 7 do you have? Windows7 enterprise service pack 1

    Have you tried to run a debug on your code? yes

    What kind of controls do you use on that form? e.g. open form, close form etc...general controls

    Have you checked the REFERENCES in the VBA IDE? no ...what do you think ?

  • This is general problem, I have more access db(.adp) , and every show this error when I want open form....

  • Are you switching/upgrading from an earlier version of MS Access? I have a vague memory that Access tightened down some security constraints (that could be undone in Settings) to warn if code was going to run.

    Rob

  • My first thought was that you are using an ActiveX control which is causing this issue. What I usually do first is checking the references (see image). Sometimes you get very weird messages if something is wrong with them or if they are missing.

    Have you tried a decompile (http://www.granite.ab.ca/access/decompile.htm)

    Just guessing...

  • My ms access dbases were created initially under ms access 2000, 2003 so I didn't make a special upgrade...

  • Here are my references...

    I didnt change references, they were set default.

    Could be a problem with code pages setting in windows7 ? ...I am just thinking

    ...my access app e.g.(pp.adp) were created in czech version of access...but it works in WinXP so I dont know ...

  • No sure if the codepage could cause this.

    Just another idea: Create a new empty adp file and import everything from the file where you have the problem.

  • I created new adp file imported all (forms, reports, modules) but the same error message.

Viewing 15 posts - 1 through 15 (of 27 total)

You must be logged in to reply to this topic. Login to reply