Incomplete Data returned |
Author |
Message |
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-05-25 06:55:40 |
I extract SalesOrderLine Info including the LineItemDescription. With Optimizer on in QB only about the first 200 characters are returned when I Query the file. When Optimizer is off all data is returned properly. Also How do I get the latest qodbc version with bugs fixed. |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-05-25 09:15:42 |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-05-25 09:56:34 |
Data is missing on every long item description. I know I can get it without optimizer but that takes 15 minutes or more. I need to update several times a day and time is important. Hope you can find a fix.
I am running QB ver 6. Have told QB support about this problem and they said they had other reports of same but that QODBC is working on it. |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-05-25 11:27:59 |
I've created a very long Service Item (ItemService) and a Sales Order using the service item and the very long SalesOrderLineDesc is displayed correctly using QODBC v6.00.155:
SELECT SalesOrderLine.TxnID, SalesOrderLine.TxnNumber, SalesOrderLine.CustomerRefListID, SalesOrderLine.CustomerRefFullName, SalesOrderLine.SalesOrderLineItemRefFullName, SalesOrderLine.SalesOrderLineDesc FROM SalesOrderLine SalesOrderLine
However, you are correct that if I use only the optimized table using the NOSYNC tag:
SELECT SalesOrderLine.TxnID, SalesOrderLine.TxnNumber, SalesOrderLine.CustomerRefListID, SalesOrderLine.CustomerRefFullName, SalesOrderLine.SalesOrderLineItemRefFullName, SalesOrderLine.SalesOrderLineDesc FROM SalesOrderLine SalesOrderLine NOSYNC
the long desciption is tunicated:
I've brought this to the attention of the QODBC Software Engineer. |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-05-25 12:42:08 |
I hope you will let me know when a fix is available.
Thanks |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-06-09 10:05:30 |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-06-16 03:56:43 |
It works for you, why not me? I am using Access 2000 and tried the pass through query and I stlll get data loss on the description field. It does work in VBDEMO. What version of Access are you using? Where can i get the full version of VBDEMO? |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-06-16 08:24:15 |
I am using Microsoft Access 2003 and QODBC v6.00.00.172 which already has changes to work correctly with Access. It should have fixed MS Query also, but it didn't. You will need to update QODBC to v6.00.00.174 (or later) when it get's released. You can check when the release is available by looking at the QODBC Updates and Bug Fixes topic in this forum.
The Visual Basic Demo program supplied with QODBC is the full version of VB Demo. |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-06-27 00:03:02 |
When will v6.00.00.174 be released? The last release I see is from April. Can I get a beta version? I really need this fix!
Thanks |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-07-08 07:14:35 |
I have updated to latest version. The original problem may have been fixed but it created another. I reset my optimizations and then ran a a query on the Salesorderline table in Access. The optimization completed and I ran the query again. It then started optimizing the Linkedinvoicetxn table. (May have the name slightly wrong.) I waited several hours for this to finish and ran the query again. It has been over 20 minutes running. My original old version when optimized finished in less than 3 minutes...though the Description was missing data. I suspect the problem is it is somehow hooked to the invoicetxn table. Please advise. |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-07-08 07:17:07 |
I should add that I also in a separate query I optimized the Invoice Line table and requeried when done and it ran quickly. Please make the SalesOrderLine table do the same thing. |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-07-08 12:38:55 |
Are you running pass-through queries ONLY for your very long SalesOrderLineDesc? You shouldn't attempt to show this column in any DataSheet view either, as it will take many calls per row to retrieve each long description, use forms only to display SalesOrderLineDesc . |
|
|
|
Gary |
|
Group | : Members |
Posts | : 30 |
Joined | : 2006-04-08 |
|
Profile |
|
Posted : 2006-07-13 02:36:20 |
My queries are now running beautifully even without the passthu and seem faster than before. Thanks for the help |
|
|
|