Quantcast
Channel: FLEXquarters.com Limited
Viewing all 290 articles
Browse latest View live

TroubleShooting: QRemote Reports "Connection to Data Source Faile...

$
0
0

TroubleShooting: QRemote Reports "Connection to Data Source Failed" When Work with 64-bit Access or Excel

Problem Description:

Setup QRemote to work with 64-bit MS Excel. The Client DSN settings are correct. But when access with "QRemote Data 64-bit" it reports error like this:

In the QRemote Server log, it reports "Connection to Data Source Failed"

Solution:

QRemote reports "Connection to Data Source Failed" error because the QODBC DSN you assigned to QRemote Data 64-bit could not connect to QuickBooks. Please check the QODBC DSN to see if it can connect to QuickBooks.

If you did not setup a QODBC DSN to connect to QuickBooks before, please refer to This Article for more information.

If you have QODBC DSN ("QuickBooks Data") and is able access QuickBooks but you are facing issue when using QRemote, it is possible that the QRemoteServer is not authorized to log into QuickBooks.  You need to accept the certificate so that QRemoteServer can connect and can extract data.

To do this you must start QuickBooks as the Administrator to your company file and switch in single user mode.

Try connecting again.

If you have accepted the certificate, then there might be chances that you might have not configured it to run as Auto-Login.

Go to the "Edit-Preferences" menu in QuickBooks.

Then select the "Integrated Applications" icon from the left side.

Then highlight one application (usually FLEXquarters QODBC) and press the "Properties" button. Check the “Allow this application to read and modify this company file”. Also check the “Allow this application to login automatically” and select a user from the “Login As” drops down. You will need to repeat this for all the applications on the list that you use.

You also need to go to DSN Setup Screen->"General" window. Input the correct company file store path. The path information can be found in QuickBooks by pressing F2 key.

If you want more detailed information about setup QODBC to auto log into QuickBooks, please refer to This Article.


How to add blank InvoiceLine in QuickBooks using QODBC

$
0
0

Problem Description:

How can I add blank InvoiceLine in QuickBooks using QODBC.

Solution:

There are empty Invoice line records in QuickBooks, and QODBC can view it too, but you may not be able to create an empty InvoiceLine in QODBC.

You cannot create an empty Invoice, neither in QODBC nor QuickBooks. But in QuickBooks, you could leave lines blank and just make sure there is at least one line with data in your invoice to create empty line records.

But in QODBC, Invoice lines are inserted by single queries, when you insert a line record, QODBC will automatically generate an invoice to contain this line item.

When the line record is null, there will be no record for the new invoice, which is not allowed by QuickBooks. So QODBC could not create an empty InvoiceLine record.

The empty InvoiceLine record must be ItemGroup/InvoiceGroupLine, Please refer : How to Invoice ItemGroups using QODBC

Troubleshooting: Error when apply payment to an invoice 'TxnID' N...

$
0
0

Problem Description:

I am attempting to apply payments to invoices I have also determined the TxnID of the Invoice I want to apply payment to and used it in the SQL code specified on How to apply payment to an invoice

I getting the error 'Error: 3120 - Object "43AC05E5-1352851019" specified in the request cannot be found.'

I have checked that I have the correct TxnID. I can do a "SELECT * from Invoice WHERE TxnID='43AC05E5-1352851019'" and it works. It's just when I try the Insert Into operation that things fail.

I have separately confirmed that I can successfully write to QuickBooks by creating an unapplied payment. It is just when trying to apply the payment to a specific invoice.

I created a new unapplied payment and then tried applying that payment to an open invoice, and that didn’t work either.

My SQL Statement:
INSERT INTO ReceivePaymentLine (CustomerRefListID, DepositToAccountRefListID, TotalAmount, AppliedToTxnTxnID, AppliedToTxnPaymentAmount, Memo) Values ('80000CDC-1275674980', '4D0000-1095982517', 1414.02, '43AC05E5-1352851019', 1414.02, 'Payment for Invoice test')

Also, I verified the invoice 43A96469-1351099713 belongs the customer 80000DC6-1286995152

Solution:

 

1) The Invoice or the Bill is already paid

OR

2) The Invoice or the Bill you are trying to adjust does not belong to the same customer/vendor as the Payment or Check is

OR

3) The ID you have specified does not exist.

OR

4) Missing ARAcount

Your query is missing ARAcount related column.

You need to insert ARAcountRefListID in your insert query.

Please add ARAcountRefListID of the invoice you want to apply for payment in your query.

The ARAcountRefListID of the invoice you want to apply the payment to is “400000-1095829128”, So please add this value into your insert query.

Please try to run below query:

INSERT INTO ReceivePaymentLine (CustomerRefListID, DepositToAccountRefListID, ARAccountRefListID, TotalAmount, AppliedToTxnTxnID, AppliedToTxnPaymentAmount, Memo) VALUES ('80000DC6-1286995152', '4D0000-1095982517', '400000-1095829128',281.98, '43A96469-1351099713', 281.98, 'Apply payment test')

TroubleShooting: ODBC call failed- Error 10004

$
0
0

Problem Description:

I am getting error ODBC call failed- Error 10004 when I am trying to connect QuickBooks through MS Access using QODBC.

Solution:

Please keep QuickBooks running, Logged in as Admin to your company file, Switch to single user mode and try to connect again with your application.

Once you are connected, close your application. On QuickBooks switch to multi-user mode and try to connect again with your application.

QB Begin Session Failed. Error = 80040408, Could not start QuickB...

$
0
0

Problem Description

Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.

Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040408, Could not start Reckon Accounts.

Begin Session errors can be caused when running ASP or other system service and not setting the "Advanced" button option of either "Use DCOM Servers" or "Remote Connector"

Solutions

Please keep QuickBooks running, logged in as Admin to your company file and try to connect.( single user mode- optional)

Your QuickBooks file should be accessible and should not be in restricted folder.

If you are trying to run QODBC/QuickBooks in auto login? And is your machine having Terminal serviced/remote desktop enabled i.e. multiple user logging in to your machine using Remote desktop connection.Then, I would like to inform you that QuickBooks SDK has a known issue with this type of Environment setup and cannot start the QuickBooks in background. (If more than one user is logged in to machine and QBW32.exe is running on more than one user account).

Workaround for the above issue.

1) Make sure you un-select the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences -- General.
Close all other QuickBooks instances of all other users and then try. (Please verify no instances are running of QBW32 under task manager --processes -- view all user processes)
OR
2) Keep QuickBooks running ( No need to login to company file , just keep QuickBooks window open ) and try connecting
OR
3) For QODBC 13.0.0.291 and upwards, under Advance tab, enable "Force Start QuickBooks", Make sure you un-select the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences -- General

If QuickBooks is already open and you are getting this error then please make sure you are not running Your Application in evaluated user context , i.e. you should not run it as "Run as administrator" .

 

Additional Information :


20140321.113817 I 3404 RequestProcessor Connection opened by app named 'FLEXquarters QODBC'
20140321.113817 I 3404 CertVerifier The Authenticode signature validated OK.
20140321.113817 I 3404 RequestProcessor OS: Microsoft Windows Server 2008 R2 Datacenter Edition Service Pack 1 (build 7601), 64-bit
20140321.113817 I 3404 RequestProcessor Current Process is elevated
20140321.113817 I 3404 RequestProcessor Current User is in AdminGroup
20140321.113817 I 3404 RequestProcessor Current Process is ran as Admin
20140321.113817 I 3404 RequestProcessor Current Process Integrity Level : 3000
20140321.113817 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113818 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113818 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113819 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113819 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113820 E 3404 RequestProcessor Could not find or create an instance of QuickBooks using InstanceFinder
20140321.113820 I 3404 RequestProcessor Connection closed by app named 'FLEXquarters QODBC'
20140321.113820 I 3404 RequestProcessor ========== Ended Connection ==========

Solution:

This is showing that your app is running in an elevated permission. QB and the app have to be running at the same level, either both as standard user or both using Run As Admin. They can not be mixed.  Try fixing the permissions and see if that resolves the issue.

This also happens when there is more than one user logged in (and has QBW32.exe running in user process) to the machine using ( remote desktop connection ) and trying to run QuickBooks with auto Login.  QuickBooks SDK shall not able to find the instance in such case.  Work around is to keep QuickBooks running, No need to login to the machine, just keep the window open.

Refer :

https://intuitpartnerplatform.lc.intuit.com/questions/834524-failure-to-connect-to-qb-13-after-update-could-not-find-or-create-an-instance-of-quickbooks-using-instancefinder

https://intuitpartnerplatform.lc.intuit.com/questions/805619-getting-error-2147220472-could-not-start-quickbooks

http://stackoverflow.com/questions/20905010/getting-error-2147220472-could-not-start-quickbooks

https://intuitpartnerplatform.lc.intuit.com/questions/817461-could-not-find-or-create-an-instance-of-quickbooks-using-instancefinder

 

Keywords : 80040418, autologin

 

Troubleshooting: Error - DoQuery Failed to get an Interface

$
0
0

Problem Description:

I am trying to insert data in Invoice table but QODBC is not allowed me to write data in Invoice table.

20131202.172908 E 2792 InvoiceStorage::DoAdd Cannot set unassigned RSB in transaction line item(s). QuickBooks error message: A row/shelf bin was expected, but an inventory site was selected. Source: src\InvoiceStorage.cpp line #513 HRESULT=0x80043973

 

I am trying to query data in Invoice table but QODBC does not show any output.

20131209.105426 E 6704 InvoiceStorage::DoQuery Failed to get an Interface ptr: Source: .\src\IteratorHelper.cpp line #360 HRESULT=0x80004005

I am trying to query data in TimeTracking table but QODBC does not show any output.

20131201.204256 E 10080 TimeTrackingStorage::DoQuery Failed to get an Interface ptr:  Source: src\TimeActFilter.cpp line #86 HRESULT=0x80004005

 

What is meaning of this error?

Solution

Please try to rebuild your company file & try again:

Rebuild your company file
To Rebuild QuickBooks company file, please select File->Utilities->Rebuild Data option

Also try changing the Iterator value to 250 or 1000 on QODBC Setup Screen--Advanced

If you are still facing the same error there might be issue with your company file and would require repairing the company file.

Please contact intuit support team and share the SDK Log files with them.

Also Refer

https://intuitpartnerplatform.lc.intuit.com/questions/798632-after-turning-off-advanced-inventory-cannot-write-invoice-via-sdk

https://intuitpartnerplatform.lc.intuit.com/questions/795014-quickbooks-error-message-a-row-shelf-bin-was-expected-but-an-inventory-site-was-selected

 


Troubleshooting: Cannot connect to QuickBooks through SSIS using ...

$
0
0

Problem Description:

I am trying connect to QuickBooks through SSIS using QODBC but I am unable to connect to QuickBooks.

I have a Read Only Desktop edition of QODBC which is included with QuickBooks Enterprise Edition.

I am getting error:“Error = 80040408, Could not start QuickBooks.”

Solution:

QODBC included with QuickBooks Enterprise Edition is Read Only edition and it can only work with QuickBooks Enterprise when using with Desktop Base application.

But to work with SSIS, you need to either use QRemote or enable “DCOM Server” in QODBC.

When you execute/set SSIS package to run as scheduled job, it runs as an Service (SQL Server is service based application).

QODBC Server Edition License is required to work with a service base application.

Please Note :  QODBC Read-Only Edition for QuickBooks Enterprise does not include QRemote License.

"Could not start QuickBooks" : Keep QuickBooks running  ( No need to login to company file , just keep QuickBooks window open ) and try connecting

Troubleshooting: Error [QODBC] Field not allowed in insert/update...

$
0
0

Problem Description:

I am attempting to add InvoiceLine records to a sample company.  I exported 15 InvoiceLine records from Quickbooks via QODBC, then built a table with these records trimmed down to what I believe are the minimum required fields, then appended this table back to the QODBC InvoiceLine linked table.

I received the following error message: ODBC - insert on a linked table "InvoiceLine" failed.
[QODBC]Field not allowed in insert (#10046)

Solution:

There are few columns, values for which automatically generated by QuickBooks SDK and are not allowed during Insert/Update. Example ListID or TxnID

You can get more information about whether a column is allowed during Insert/Update or not, by typing below command in VB Demo:

sp_columns TableName

For Example: sp_columns InvoiceLine

The command will return the schema rules of selected table (In this example it is InvoiceLine), including information about whether a column is updatable or insertable.

When you try to insert non insertable field in your query, QODBC will show error "[QODBC]Field not allowed in insert ".

So when you get "Field not allowed in insert" error, please check your insert statement it may contain one or more non insertable fields. Please remove non insertable fields from query and try to execute the SQL statement again.

When you try to update non updateable field in your query, QODBC will show error "[QODBC]Field not allowed in update ". So when you get "Field not allowed in update" error please check your update statement, it may contain one or more non updateable fields. Please remove non updateable fields from query and try to execute the SQL statement again.

 

Tags : Table Field Types, Field Types, What does field type mean

 


Known issues with QuickBooks 2014 SDK

$
0
0

Environment

QuickBooks 2014

QODBC 14.0.0.298

 

QODBC is an ODBC driver for QuickBooks. It uses the QuickBooks SDK to communicate with QuickBooks & QuickBooks company file. QODBC can show/fetch only those information which are exposed/provided by QuickBooks SDK.

There are a few changes in the QuickBooks SDK for QuickBooks 2014 that return incorrect data, causing QODBC to fail.

Below are the known issues with QuickBooks SDK.

1)  InventoryStockStatusByItem , InventoryStockStatusByVendor & InventoryValuationDetail  does not shows any result.

2) Customer table  "Contact" Field is not returning data.

3) A few of the report(s) show detail information which earlier showed summary information. Rows are no longer grouped as "--Multiple--".

4) A few of the report(s) show summary information which earlier showed detail information. Rows are now grouped as "--Multiple--".

 

I would suggest you to contact Intuit if you need to use the data that has been disabled by this recent update.

QRemote Initialization Error , Error: Listening failed. Please re...

$
0
0

 

Problem

QRemote Initialization Error ,

QRemote Error: Listening failed. Please restart application

QRemote Closing in 15 Seconds.

 

Solution

There might be multiple instances of QRemoteServer.exe running or Machine would require Restart.

FYI, QRemote Server reports “Error: Listening failed. Please restart application” is usually because that there is already one QRemote Server running in the system.

Please open Windows Task Manager, go to “Processes” window. Select “Show processes from all users” option. Then find “QRemote Server.EXE” at the process list, and then terminate this process.

After you make sure there is no “QRemote Server.EXE” running in the system, please start QRemote Server to see if the problem is still there.

If you are on a Terminal Service Machine/Remote Desktop enabled machine and have multiple user logged in.
QRemoteServer gets installs as a startup for all the users, and the 1st instance of QRemoteServer will be used to connect to QODBC DSN/QuickBooks.
In case you wan to change this, you may use msconfig, remove QRemoteServer from Startup. Then manually add the user;s startup folder who will be using the QRemote/QuickBooks.

 

TroubleShooting:QODBC Hangs When Trying to Execute Query or View ...

$
0
0

TroubleShooting:QODBC Hangs When Trying to Execute Query or View Tables

Problem Description:

When executing a simple query like:

SELECT * FROM Invoice

Application and QuickBooks will both gets hang, and it Does Not Respond.

Then After, application is forced to close, QuickBooks becomes normal again.

Solution:

This may be case of your Optimizer file is corrupted or QuickBooks Company file needs Rebuild/Repair

Close All application using QODBC & un-select "Use Optimizer" (QODBC Setup Screen->Optimizer Window->Uncheck "Use Optimizer" option).

Then use our test tool VB Demo to test again to see if the problem is still there.

If about does not resolve the issue, You may have to Rebuild your company file.  Please refer : How to Rebuild an QuickBooks Company File

 

And if QODBC works with optimizer turning off, then there might be problem/corruption in your optimizer file.

For QODBC 13.0.0.292 or above, Reseting Optimizer file is on single click, you can click "Reset Optimizer File" and then   Run     sp_optimizefullsync ALL command in VB Demo:

Refer :  How to execute SP_OPTIMIZEUPDATESYNC or SP_OPTIMIZEFULLSYNC for Selected Tables


Otherwise follow below steps

You need to reset your opt file store path. You can simply find the path setting at QODBC Setup Screen->Optimizer Window.


The default path is "%UserProfile%\QODBC Driver for QuickBooks\Optimizer", please set it to "%appdata%\QODBC Driver for QuickBooks\Optimizer" or use other folder which you have full authority to access it.

After the path setting is completed,

Navigate to that Path,  Start -> Run -> and then type the Optimizer file path, Delete the .OPT ( corresponding to your company file )

Please run this command in VB Demo:

sp_optimizefullsync all


This command will re-optimize all QuickBooks data and create a new opt file at the folder you assigned.

Refer :  How to execute SP_OPTIMIZEUPDATESYNC or SP_OPTIMIZEFULLSYNC for Selected Tables

FYI, In-case you are using connection string or linked table in MS Access to connect to QuickBooks, please remove the former connection string or linked tables and re-build a new one to make sure that it points to the new opt file store path.

TroubleShooting: Expected lexical element not found

$
0
0

TroubleShooting: Expected lexical element not found

Problem Description 

When trying to execute a query statement I get the error message " Expected lexical element not found "

Solutions

It seems to be issue in the SQL Statement. Please check all the fields name and table names.  Normaly this could be a typo error on the field name in your SQL Statement.  To know more about the fields and data layout, please Click Here

 

Another Possible Problem & Solution:

Problem Description:

When I issue below SQL statement:

SELECT Desc FROM Charge 

I get "Expected lexical element not found: = <identifier>"

However, if I issue

Select * from Charge

Then, I get a full output, with one of the columns named "Desc".

Why can't I query for the column by name?

I have tried this through the VB demo and through a C# program as well.


Solution: 

I would like to inform you that Desc may be a reserved word in SQL due to this you are getting this error. I kindly request you to please put quotes around "Desc". Please use below query which does not issue an error:

SELECT "Desc" FROM Charge 



TroubleShooting:Table TimeTracking or Transaction Table is Blank

$
0
0

TroubleShooting:Table TimeTracking / Transaction Table is Blank

Problem Description:

The TimeTracking / Transaction table always return null/ no rows as a results. Tried to reset QODBC optimizer, but doesn't work.

Solution:

Please update your QuickBooks to latest version & check issue again.

Also, please make sure that short date format in Regional Setting is not set to “yyyy mmm dd”. If your short date format is “yyyy mmm dd”, then you might face this issue. 

We have received multiple reports about table TimeTracking not returning any data, and we found that this is usually caused by Corruption in Company file. To locate your issue, please test the same query on another company file, such as sample company file, to see if it can bring data back.

Also try adding limiting the result set by adding filters and apply date range.

If the same query can bring data back on other company files, then please try to rebuild your company file via File->Utilities->Rebuild Data in QuickBooks to see if it can fix your issue.

Rebuild Company file

And if rebuilding does not work, please contact Intuit for more help.

And if QODBC cannot extract TimeTracking/Transaction data on other company files, please post a ticket to us so that we can do a further investigation on the issue.

 

For Advanced Troubleshooting Click Here

 

Troubleshooting: Slow Performance / Cannot Get Full Records From ...

$
0
0

Troubleshooting: Slow Performance / Cannot Get Full Records From QuickBooks / How to find missing data

Problem Description 1:

1.QODBC is showing Partial data or few of my data is missing in the result set.

2.I am able to create an IRL and IR using QODBC and able to see the IR in QB. But when I am running the VB DEMO or running SQL using QODBC it says record not found. I am unable to retrieve anything thing that I added after 11/18. But Can see in the data in QB and process it in QB.

I also tried creating a Bill in QB and tried to use a simple SQL to run in VBDEMO nothing shows up.

 

Problem Description 2:

We have a custom report that summarizes custom data fields in Quickbooks. When we updated from QB ES 15 to 16, the report stopped working stating that we needed to update the QODBC driver version. We installed the version within QuickBooks, however, the report would return 'blank' reports using a list of 30-40 different parameters. An investigation by a Crystal developer revealed that the report stops returning ANY data at a certain number of parameters passed, but works as designed up to that point. We didn't see this limitation prior to the upgrade from 15 to 16. The report is used to predict and budget revenue.

 

Problem Description 3:

Every two weeks, we use an access database to read employee paycheque details from Quickbooks.

The last two times, the first time we ran the query, we were missing exactly one record.

Both times, simply re-running the query gave us the full expected recordset.

We did not even close and re-open the database or Quickbooks between each running of the query.

What could be causing this?

 

 

Problem Description 4:

Last Friday we ran updates to Quickbooks 2015. For some reason, our MS Access application stop getting results from queries. I noticed VB Demo still works.

I even tried a simple query and just hangs with the circle

 

 

Problem Description 5:

When I filter the QODBC Transaction Table to only show Income, Expense, Other Income and Other Expense and only transactions in our current Fiscal Year, it does not match the QB generated P&L Report for the same time frame. It seems like random sections of certain journal entries are missing from QODBC. I tried "ReBuilding" the QB Company File, but it did not help. Any ideas?

 

Solution:

1.Rebuild your company file

To Rebuild QuickBooks company file, please select File->Utilities->Rebuild Data option:

Please make sure you follow the instruction of QuickBooks and make a backup before rebuilding.

 

2.Delete Optimizer file

 

Check the Use Optimizer option to reactivate and reset the Optimizer.

See also: How do I setup the QODBC Optimizer? Where are the Optimizer options?

 

In Case, your Optimizer file is Corrupted you can delete the Optimizer file and QODBC will generate a new one in the next data connect.

For QODBC 13.0.0.292 and Above, you can also Reset the Optimizer file on a Single Click from
QODBC Setup Screen->Optimizer Window->Reset Optimizer File(s)

 

 

Also Refer: How to Remove Optimizer file

If above steps do not work, Please follow below Manual Steps for resetting Optimizer

1) Close all applications other than QuickBooks/Reckon.


2) Find the file with .opt extension at the path you had assigned to "QODBC optimizer" and delete the optimizer file.
(the default path is %AppData%\QODBC Driver for QuickBooks\Optimizer.
Here are the steps to locate the folder
Click on Start Button,
Click on Run,
Type the below command & press enter
%appdata%\QODBC Driver for QuickBooks\Optimizer
This should Open a folder)

And also, please refer to How to switch OFF or RESET the QODBC Optimizer for more information about resetting QODBC optimizer.

 

3. Build Optimizer file

Please run below command in VB Demo:

 

sp_optimizefullsync ALL
 

Or

sp_optimizefullsync SalesOrder
sp_optimizefullsync Invoice


 

 

 
 
Please Note: You need to optimize parent table only. There is no need to optimize child table separately.

For Example:

When you optimize "Invoice" table, QODBC will automatically optimize the child table "InvoiceLine", i.e Invoice & InvoiceLine will be optimized.

When you optimize "Bill" table, QODBC will automatically optimize the child tables "BillItemLine' & "BillExpenseLine", i.e Bill, BillItemLine & BillExpenseLine will be optimized.

Please refer: How to execute SP_OPTIMIZEUPDATESYNC or SP_OPTIMIZEFULLSYNC for Selected Tables


The sp_optimizefullsync command will bring some data to a local cache to increase retrieval performance for queries. I would like to suggest you to please let run above command completely. Above command may take some time depends on your records in QuickBooks. It may take 4-24 hours or more depends on the number of records in QuickBooks company file. Please let this command run completely do not kill this command. It is not advisable to kill/close the application while it is building the Optimizer file.


4. Close VB Demo.

 

5. Enable QODBC Status Panel:

Please also enable QODBC status panel via QODBC Setup Screen->Message Window->Select "Display Driver Status" and "Display optimizer Status" options.

 



And then the next time you run a query, if you see “Waiting for QuickBooks”, it means QuickBooks is taking the time to process the request. There will be a status panel at the lower right corner of your screen, will be shown a window with information on what QODBC is working at. Please note the step on which QODBC spends most time or get stuck.

 

6. Start your application again & test again.

 

Additional Information:

Test Without QODBC optimizer

First, please turn off your QODBC optimizer (QODBC Setup Screen->Optimizer Window->Uncheck "Use Optimizer" option), then use your query in VB Demo to test again to see if it can bring back those missing records. And if it works, then please follow the below steps

 Or

To temporarily bypass your optimizer settings and extract the latest information you can add the unoptimized tag after the table name like this to your queries:

    select * from InvoiceLine unoptimized where TxnDate >= {d'2006-03-06'}.


If Above Solutions doesn't work, please post a ticket to us and we will do a further investigation on your issue.

 

Balance,CurrentBalance,QuantityOnHand is missing value or showing...

$
0
0

Problem Description

Fields related to Balances and QuantityOnHand is showing Null value or is Missing Value, where in QuickBooks is showing correct information.

e.g When using below query with Optimizer On it does not shows the detail but when Optimizer is turned OFF it can show correct value

SELECT QuantityOnHand FROM ItemInventory where Name = 'MYPRODUCT'

Is there a way to get QuantityOnHand Keeping Optimizer On

Solutions

Change the following value on the Optimizer tab and try again.

QODBC Setup screen --> Optimizer --> Under "For balances and stock quantities" select Either "Dirty Reads"/"Real Time"

 

For balances and stock quantities: the option Nulls - will return NULLs for all fields that cannot be kept in sync, Dirty Reads - means return the most current value that was loaded into the optimizer cache, and Real Time uses the slower method to get the data directly out of QuickBooks making sure you get the most current value for the requested fields. (Real Time is the previous method used).

For More Details Please Refer : QODBC Setup Options


Getting limited number of records or Few of the records is Missin...

$
0
0

Troubleshooting: Getting limited number of records or Few of the records is Missing in QODBC Table result

Problem Description

     1. When I Query my tables e.g Bill or Customer, I noticed QODBC is not returning all the records and seems few records are missing.

      We have a number of invoices that don't exist in the linked invoice table. The invoices can be pulled up in Quickbooks but searching for the invoice number in the Refnumber field doesn't return any results.

    2.I am able to create an IRL and IR using QODBC and able to see the IR in QB. But when I am running the VB DEMO or running SQL using QODBC it says record not found. I am unable to retrieve anything thing that I added after 11/18. But Can see in the data in QB and process it in QB.

I also tried creating a Bill in QB and tried to use a simple SQL to run in VBDEMO nothing shows up.

Solutions

The reason could be QuickBooks Company file requires Rebuild/Verify or QODBC cache file/Optimizer is corrupted or some mismatch happened in the cache file.

Try below steps to see if it fixes the issue

 

 

1.Rebuild your company file

To Rebuild QuickBooks company file, please select File->Utilities->Rebuild Data option:

Please make sure you follow the instruction of QuickBooks and make a backup before rebuilding.


2.Rebuild Optimizer file

Close all your application
Start VB Demo
Connect to your DSN
execute the below command
sp_optimizefullsync Bill
sp_optimizefullsync Customer

 

Or ( For All the tables)

Close all your application
Start VB Demo
Connect to your DSN
execute the below command
sp_optimizefullsync ALL

 

 

Also Refer

VB Demo Missing

TroubleShooting:Cannot Get Full Records From QuickBooks

How to switch OFF or RESET the QODBC Optimizer

HY111 database connector error invalid bookmark value

$
0
0

 

"HY111 database connector error invalid bookmark value" on crystal report when refreshing report.

 

 

 

Solutions

This could be issue with the company file, or Optimizer.

I kindly request you to follow below steps and let us know if that resolve the issue.

In QuickBooks Verify & Rebuild Company file
On QODBC Setup Screen -> Optimizer -> Turn On the Optimizer and Click Reload All Data.
Try your SQL Statement with VBDemo/Crystal Reports

If you are still facing issue, Login to any Sample company file of QuickBook and follow above step.

If Sample file can work, I guess this could be issue with your company file any some data on your company file.

If Sample file can NOT work, I guess this could be issue with QuickBooks or QODBC Configuration, I would suggest to try the report/query on a different machine.

Troubleshooting:Cannot find QODBC Driver/QuickBooks Data under sy...

$
0
0

Troubleshooting: Cannot find QODBC Driver/QuickBooks Data under system DSN with any application other than the VB Demo

Problem Description

Testing under 64-bit system, when using VB Demo test application, the user can see DSN (QuickBooks Data) in the ODBC manager, but when using other application or try to configure the DSN through ODBC manager, user cannot find the DSN.

Solution

FYI, under the 64-bit system, there are two ODBC managers, one is for 32-bit and the other is for 64-bit. QODBC is 32-bit, so the default DSN (QuickBooks data) is 32-bit too. You cannot find it in 64-bit ODBC manager.

Please use 32-bit ODBC manager to view and modify QODBC DSN.

1.Click  Start -- > All Programs -- > QODBC Driver for use with QuickBooks  -- > Configure QODBC Data Source.

QODBCStartMenu.png

Alternative : The 32-bit ODBC manager can be found at C:\windows\sysWOW64\odbcad32.exe.

 

Please refer to this article: Vista/Windows 7 and 64 bit and QODBC for more detail information.

And If the application cannot find QODBC DSN, it is probably because that the application is 64-bit. QODBC is 32-bit and it can not directly work with the 64-bit application. Please refer to this article: How to Configure QODBC to Work With 64-bit Applications for more information if you want to use QODBC with 64-bit applications.

QODBC error 80004005 when trying to run .vbs file on 64 bit machi...

$
0
0

Problem

Created a VBS refering - http://support.flexquarters.com/esupport/index.php?/Default/Knowledgebase/Article/View/506/57/examples-of-how-to-use-qodbc-via-visual-basic

On Executing VBS an  Error message came up - "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application; Code: 80004005; Source: Microsoft OLE DB Provider for ODBC Drivers"

Solution

 

Since you are using 64-bit system, your VBS will be execute as 64-bit (by default).

QODBC is 32-bit driver, and can work with 32-bit applications. A 64-bit applications cannot talk to a 32 bit Driver and same is with 64bit application to 32 bit Driver.

For 64-bit applications use QRemote (which is a 64-bit Driver driver).

Solution 1 You can try to use QRemote to bridge QODBC and your application. Here is an article about how to use QRemote: http://www.qodbc.com/qremoteconnect.htm

Solution 2 and there is another solution for you issue. Please call your VBS as 32 bit. Please follow the steps below:

1) Click Windows Start

2) Click Run, in the window, type "%windir%\SysWoW64\cmd.exe"

3) Click OK, then type "cscript vbscriptfile.vbs" in the cmd window

This will make your VBS run in 32-bit mode even thou you are in 64-bit machine.

QuickBooks Data DSN Not Showing Up In ODBCAD32.exe ODBC Data Sour...

$
0
0

Summary about Using 32-bit ODBC driver on 64-bit platforms

      On 64-bit platforms, 32-bit ODBC drivers are available to 32-bit applications, but not to 64-bit applications. What determines which ODBC driver architecture used is whether your application is 32-bit or 64-bit not whether your client platform (or database platform or DBMS) is 32-bit or 64-bit. Since QODBC is a 32-bit only ODBC driver, the only applications that can access it are 32-bit applications.

 

 32 bit Data Source to show QODBC under 64 bit system

Run the default system data source:    

   Start -> Control Panel -> Performance and Maintenance -> Administrative Tools -> Data Source (ODBC)

     This brings up Data Source listing the 64-bit drivers

As QODBC is a 32-bit driver, this will not show QODBC Driver for QuickBooks / QuickBooks Data on the list.

Close the Data Source and all its windows.

1.Click  Start -- > All Programs -- > QODBC Driver for use with QuickBooks  -- > Configure QODBC Data Source.

QODBCStartMenu.png

Or

2.   Run the 32 bit ODBC admin utility to see data source:

      C:\windows\sysWOW64\odbcad32.exe

 

Tags: ODBCAD32, QuickBooks Data, 64 bit, Driver Not Showing, No Driver listing

Also Refer:

How to setup QODBC for Auto-login into QuickBooks

How to create or configure a QODBC DSN

Viewing all 290 articles
Browse latest View live