MSVBVM60.dll Error in QuickPOS

Legacy KB ID: 3278

Question

Why do I get a MSVBVM60.dll error when Transferring data from QuickBooks into QuickPOS or in QuickPOS?

Answer

This error doesn’t tell us a lot but what we do know is that it means there is something wrong with the database.

Try the following suggestions in the order below:

1. Try a Compact of the QuickPOS database in QuickPOS Administrator.

2. Have they just changed an item in QuickBooks? When setting up an item have, they entered a barcode number or accidentally typed a letter in custom fields, Price Level 2 or 3?

QuickPOS needs to calculate GST on the price level fields, a barcode number is too long to calculate and/ or unexpected characters will cause QuickPOS or QuickPOS Administrator to crash with this error.

1. A quick way to check the item list for discrepancies is to export the item list from QuickBooks and open the file in Excel. When you open the file in Excel you will get an Import Wizard, click Next to step 3 of the wizard and scroll down and across to find the columns named CUSTFLD1 and

2. Highlight each column and change the Column data format from General to Text. Click Finish to open the file. In Excel go across the page and check the data in the fields CUSTFLD3 and 4, these are the Price Level fields.

3. Has there been a change made in any of the other lists we import from QuickBooks for example, Employee list, Chart of Accounts or Customer Accounts. To help find any discrepancies with these lists open them in Excel. See document ‘Opening POS item list in Excel’ document for instructions.

4. If all else fails make sure you have the licence key and registration number written down for QuickPOS Administrator then go into regedit > HKEY_CURRENT_USER > Software > VB and VBA Software Programs > QuickPOS Administrator and delete the Registration directory.

Open QuickPOS Administrator and re-enter the license and registration details.

How did we do?

How do I use POS to sell Consignment Items?

"Runtime error 339. Component POSTouchKeyboard.ocx ...not correctly registered."

Related Articles

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)