Solved

DB.Execute sInvoiceQuery, dbSeeChanges

Posted on 2008-10-10
7
1,196 Views
Last Modified: 2008-11-16
Using Access 2000 and i get a DAO error when running this command:
DB.Execute sInvoiceQuery, dbSeeChanges

*I am using SQL as the backend that I just mirgrated
DB.Execute sInvoiceQuery, dbSeeChanges

Open in new window

0
Comment
Question by:IsdNG
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
7 Comments
 
LVL 57
ID: 22687718

  What error are you getting?  You will see an error if another user is editing the data your working with.

JimD.
0
 

Author Comment

by:IsdNG
ID: 22687875
I am getting the following error 3146 ODBC - call Failed DAO.Database. Since i migrated my cust table to SQL i had to add "dbSeeChanges" to my Rs commands.  I am having a problem when adding it to my EXECUTE command. Help
0
 
LVL 57
ID: 22689119
 
  3146 is a general server side problem.  Any number of things can be causing the error.  What is it that this ODBC call is doing?

  First thing I'd check however is the data type on the migrated tables.  Did you let the upsizing wizard determine the field types or did you add them yourself?  I'd also check and ensure that every table has a primary key.

JimD.
0
 

Author Comment

by:IsdNG
ID: 22689644
Sorry I am new to this...
    > Recently Moved my Customer table from Access to SQL.
    > Using Access 2000 I  had to add DBSeeChanges to all my Rs connections which is
        working fine.
    > THE PROBLEM: I have one line of code that execute's a query  DB.Execute Query1"
                               which is causing the DAO error.
                               I modified this line to read  DB.Execute sInvoiceQuery, dbSeeChanges
                               and its still not working.  Can you help?
0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 125 total points
ID: 22689980
<<Sorry I am new to this...
    > Recently Moved my Customer table from Access to SQL.
    > Using Access 2000 I  had to add DBSeeChanges to all my Rs connections which is
        working fine.
    > THE PROBLEM: I have one line of code that execute's a query  DB.Execute Query1"
                               which is causing the DAO error.
                               I modified this line to read  DB.Execute sInvoiceQuery, dbSeeChanges
                               and its still not working.  Can you help?>>

  Yes, I understand all that, but as I said, 3146 is a generic server side error message.  It can happen for any number of reasons.  I've already given you a couple of possible problems (data types or no primary key).  It can also be lack of permissions.

  What I would do is check out the table(s) that are being delt with in the Execute and see if you can enter records manually in those tables from SQL server.  Then from Access, attach to them via ODBC and see if you can manually edit the tables there.

  At some point in doing that I think you'll find your problem.

JimD.
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Entering a date in Microsoft Access can be tricky. A typo can cause month and day to be shuffled, entering the day only causes an error, as does entering, say, day 31 in June. This article shows how an inputmask supported by code can help the user a…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question