Announcement

Collapse
No announcement yet.

Please help me to connect to msaccess using ado db

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Please help me to connect to msaccess using ado db

    HI FRIENDS,

    DUE TO PROBLEMS WITH SCRIPTCASE USING THE ODBC ACCESS, I HAVE TO INTENT CHANGE ALL MY CONNECTIONS TO ACCESS ADO.

    BUT I FOLLOW ALL THE STEPS OF DOCUMENTATION, BUT CAN'T CONNECT TO MY .MDB DATABASE

    I HAVE ENABLED COM (TEST USING SCRIPTCASE DIAGNOSE)

    i put the path d:\banaplast_bs.mdb
    and left blank user and password textbox
    and receive this message :
    La operación de múltiples pasos de OLE DB generó errores. Compruebe los valores de estado de OLE DB si es posible. No se realizó ningún trabajo.

    i put the path d:\banaplast_bs.mdb
    and put "Admin" as user and left blank password textbox
    and receive this message :
    Source: Microsoft JET Database Engine
    Description: No se pudo encontrar el archivo ISAM instalable. Declaration of ADODB_ado_access::connect() should be compatible with that of

    i put the path d:\banaplast_bs.mdb
    and put "Admin" as user and "root" as password
    and receive this message :
    Source: Microsoft JET Database Engine
    Description: No se pudo encontrar el archivo ISAM instalable. Declaration of ADODB_ado_access::connect() should be compatible with that of ADOConnection::Connect()


    HELP ME !!!!!!!!!!!!!!!!!

    AQUILES
    Attached Files

  • #2
    I don't know what's the cause of this, a misconfiguration or a bug. But fastest way might be to port to MySql. MsAccess is perhaps a great desktop database, but not in a multiuser webenvironment imho.
    Albert Drent
    aducom software netherlands
    scriptcase partner, reseller, support and (turn-key) development
    www.scriptcase.eu / www.scriptcase.nl

    Comment


    • #3
      Hi Albert,

      but the funny thing is that everything worked fine until version 20, since that version everything worked poorly with msaccess.

      It listed the querys sc no, not bear fields interspersed with points.
      currently only the problem of not listing the querys persists.

      Yesterday I did another test, another new pc proceeded to download a new copy of ScriptCase, and repeat the steps to test if my old pc had been misconfigured, but everything worked poorly (v6.0039) equal in both.

      please, why are so proud, a Mercedes Benz hasa fails, why not accept that it is a simple change that made in the function which makes nm_odbc_access ignore the filters that are put in the connection settings.

      accept that failure is not MsAccess, the fault is within ScriptCase, and this simple error is 6 months and unresolved.

      please proceed yourself to that test:

      create a small database with a table MsAccess anyone and any query.

      Now click the link ODBC

      then connect the odbc ScriptCase and proceed to create a new grid binded to the query.

      These you can not view query in the datasource list!!

      THAT IS ALL!

      Is your machine? is your MsAccess? NO, is your ScriptCase!

      Comment


      • #4
        Which ms access version?
        I think you should try a commandline php connection first (example: http://www.actionscript.org/forums/s...d.php3?t=21969).
        If you get that to work then you are already almost done.
        Be sure to check your path variables for your webserver (use process explorer if needed from sysinternals tools). I have had an error where I could not connect to oracle. In the end it just was that the path where
        the needed dll's lived were not in the path, hence no connection. The easiest way is to change the path in the environment variables, then you know it should always start.

        Comment


        • #5
          Hello Aquiles,

          Does the database requires a User and Password to connect?

          Is .NET and COM support enabled? See this image: http://downloads.scriptcase.com.br/d.../img/372_1.png

          Have you tried to connect via ODBC? It worked?

          regards,
          Bernhard Bernsmann

          Comment

          Working...
          X