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 : ODBC with AccessSearch Forum

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

 New Topic 
 
 Post Reply 
[1]  
 ODBC with Access 
 Author   Message 
  Chris 
  
 Group: Members 
 Posts: 3 
 Joined: 2006-04-29 
 Profile
 Posted : 2006-04-29 05:33:52
I currently have a query linked to the SalesOrderLine  Table.  The query runs fine, pulls all the pertanant data.  However when someone changes a sales order,  when the data is pulled from quickbooks, it duplicates the orders.  Quickbooks is keeping track of the order before it was modified and will continue to pull it.  Is there a way to turn that off so that when a order is modified that it is updated and the older version is not kept.  Or is there a field in the table that shows modified orders that i can turn off in access.

thanks 

 
Chris
Front Porch Classics
Logistics Manager 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-04-29 20:25:35

First, please make sure that you're running QODBC v6.00.00.155 (or later). If the problem still persists with QODBC v6.00.00.155 (or that's what you are running already), change the query to use the unoptimized tag after the table name, for example:

SELECT TxnNumber, CustomerRefFullName, TxnDate,
RefNumber, TotalAmount FROM SalesOrderLine unoptimized
where IsFullyInvoiced = FALSE  

 

  Top 
  Chris 
  
 Group: Members 
 Posts: 3 
 Joined: 2006-04-29 
 Profile
 Posted : 2006-05-02 05:24:48
yes i am running that version. My query is much longer than that, where would i place that if i have alot of sql lines? Where exactly can i place the tags?  Unoptimize and or Verify? 

 
Chris
Front Porch Classics
Logistics Manager 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-05-02 08:14:18

You can override your QODBC Optimizer configuration screen settings to suit what you are actually doing by using the following tags after the table name:

VERIFIED | VERIFY - Forces Full Resync with QuickBooks on the optimized table before Query starts
CALLDIRECT | UNOPTIMIZED - Passthru query directly to QuickBooks - use no optimizations
OPTIMIZE | OPTIMIZED | NOSYNC - Passthru query to optimized table directly for maximum speed

Examples:

select * from InvoiceLine UNOPTIMIZED
select * from InvoiceLine NOSYNC
select * from InvoiceLine VERIFIED

To read all the InvoiceLines directly out of QuickBooks use:

select * from InvoiceLine UNOPTIMIZED

Or you can resync your optimized InvoiceLine table by first doing:

sp_optimizefullsync InvoiceLine

then read directly out of the optimized table by doing:

select * from InvoiceLine NOSYNC

This is very f...a.......s.................t.

Another good example of using NOSYNC would be to get for example all invoicelines before 2003:

SELECT * from InvoiceLine NOSYNC WHERE Txndate < {d '2004-01-01'}

as invocies before 2004 don't ever change, you can read them directly from the QODBC Optimizer. You just need to use unoptimized for crtical operations like Sales Commisions etc.

See: How do I create a Pass-Through Report using Microsoft Access 2003? for more.

 

  Top 
  Lloyd 
  
 Group: Members 
 Posts: 2 
 Joined: 2006-11-03 
 Profile
 Posted : 2006-11-03 19:15:21
I am a newbie, having issues with MS Access 2003 truncating memo fields.  Specifically, the field SalesAndPurchaseSalesDesc (containing lengthy product descriptions) in the table ItemNonInventory is truncated when I access the linked table in Access.  I tried the VB Demo application using the same ODBC data source, and the results are not truncated.  I also tried importing the table to Access instead of linking to it, but the field was still truncated.  So, I believe the problem is in Access.  The length of the string that gets passed through does not seem to be limited to 255 characters.  I checked the length of the passed data, and it ranges from 884 characters on down, with all of the larger length fields coming from truncated records.  In other words, the records are all truncated at different lengths.  Any insight on this would be appreciated. 

 
Lloyd Smith
Cortech Solutions, LLC 
 
  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-11-03 20:14:05
Please see: Incomplete Data returned for further information.

See also: QB Multi-Line fields not displayed properly in MS Access reports 

 

  Top 
  Lloyd 
  
 Group: Members 
 Posts: 2 
 Joined: 2006-11-03 
 Profile
 Posted : 2006-11-08 10:03:06

Tom: I updated to 7.00.00.199 and I get the complete memo field records.  Thanks for the assistance!

Lloyd Smith

 

 
Lloyd Smith
Cortech Solutions, LLC 
 
  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to