Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : Select Name from EmployeeSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v9 Forum

 New Topic 
 
 Post Reply 
[1]  
 Select Name from Employee 
 Author   Message 
  Steve 
  
 Group: Members 
 Posts: 7 
 Joined: 2009-01-16 
 Profile
 Posted : 2009-01-16 16:38:33
This simple string crashes Quickbooks 2008 every time. I run it from the VBDemo interface and it causes an unrecoverable error that shuts down Quickbooks. Any Ideas?
Thanks
Steve 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2009-01-17 09:46:21
Works fine for me. Is this the only query that fails? 

  Top 
  Steve 
  
 Group: Members 
 Posts: 7 
 Joined: 2009-01-16 
 Profile
 Posted : 2009-01-17 11:26:25
Yes this is the only query that causes problems. In an attempt to find which table a person exists in after finding them in ENTITY I query CUSTOMER, then VENDOR, then EMPLOYEE and it causes a fatal error on EMPLOYEE. I'm thinking that the data got scrambled when I imported the chart of accounts and all the list info into this new quickbooks company. Is there a way in Quickbooks to fix that?
Thanks Steve 

  Top 
  Steve 
  
 Group: Members 
 Posts: 7 
 Joined: 2009-01-16 
 Profile
 Posted : 2009-01-18 08:05:36
This issue was solved by rebuilding the quickbooks data file
Thanks
Steve 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to