Problem in Data Request through ODBC ACCESS Driver

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ashutoshvyas
    New Member
    • Jul 2007
    • 18

    Problem in Data Request through ODBC ACCESS Driver

    Hello All.
    Specially ADejii.

    I had generated a report in VB. For that purpose i am using ACCESS database. This database is connected via Microsoft Jet 4.0 OLE DB provider, and it is working well.

    Now i has changed provider for other purpose so i am getting problems in report generation.

    Provider : Microsoft OLE DB provider for ODBC Drivers
    Connection Status : Test Connection Succeded.

    Error in passing parameter obtained through text box in VB.
    Code:
    .command1 CDate(text1.Text)
    I want to know that is it a valid method or not ? if not what should be the syntex.

    Error : Run-time error '-2147217887 (80040e21)':
    [microsoft][ODBC Microsoft Access Driver]Invalid precision value

    Thanks.
  • Stang02GT
    Recognized Expert Top Contributor
    • Jun 2007
    • 1206

    #2
    Originally posted by ashutoshvyas
    Hello All.
    Specially ADejii.

    I had generated a report in VB. For that purpose i am using ACCESS database. This database is connected via Microsoft Jet 4.0 OLE DB provider, and it is working well.

    Now i has changed provider for other purpose so i am getting problems in report generation.

    Provider : Microsoft OLE DB provider for ODBC Drivers
    Connection Status : Test Connection Succeded.

    Error in passing parameter obtained through text box in VB.
    Code:
    .command1 CDate(text1.Text)
    I want to know that is it a valid method or not ? if not what should be the syntex.

    Error : Run-time error '-2147217887 (80040e21)':
    [microsoft][ODBC Microsoft Access Driver]Invalid precision value

    Thanks.


    You said you have changed the provider and everything was working good before you made this change?

    I have gotten some pretty goofy errors with linked databases and not using the correct drivers. I could be way off base here but i would just check to make sure that you are using the right driver and maybe undue the change that you made and see if things work again.

    Comment

    Working...