I have been using a compiled VS Studio 2005 program I wrote for a year ago with no issues to write invoices into QB from a text file.

When I upgraded to ver 7.0.0.0.214, and now operate this program,  I get the "activation" error as if it will not "write" to QB anymore.  This error during an "update()" to the invoice line item file - this code has worked flawlessly for hundreds of times before this over the past year.

What does this error mean?  I can write information back to QB Enterprise v7r8P using Access - I am not sure if this is the result of SP1 in Visual Studio or simply the updated driver.

Can I get a link or email me the download of your last release so I can test this program more effectivaly?  The error code in "details" is -2147467259

What other info can I give to you for resolution?  Thank - Victor

Did you install the full version of QODBC or the stripped down Enterprise version? Have you got a CD Key and does the "About" tab in the QODBC Setup Screen show the Serial Number to be W07xxxxxxxxx ?

Did you purchase a new CD Key for QODBC v7 for QuickBooks 2007? 

The CD key I used is the one I got from Mark - it is a full version.  My serial number is D07xxxxxxxx not W07xxxxxxx -

This key has worked with this configuration before (I have 15 licenses)

I should be using the 'full' version - I even uninstalled, deleted the directed for QODBC, deleted any references to QODBC in the windows/system32 directory, rebooted, and then re-installed.

Any more ideas?  I still think there is incompatability in 7...214 - can I get a previous release to check out this theory?

Vic

Is your OEM Pack Read/Write? Check the about screen. Please download our version of QODBC from: How can I get the latest version of QODBC? 

Note: If your QuickBooks Enterprise company file is accessed using the FREE QODBC Enterprise Edition (that doesn't require a CD Key), your company file will be hard wired as read only access. This is under strict instructions from Intuit. All QODBC users on the network must use the full read/write version of QODBC (that requires a CD Key).

I may have tried to use the utilies and add QODBC option from QB Enterprise on this computer earlier - are you saying this is causing the problem on my computer - that I have activated (tried out) the read only version from the QB System?

We did finally get the update to work on an older computer tonight, running XP Pro, but it is using the same company file and same VS Projects?  Why are you saying that the company file is "hard wired" to read only access.  How do I change this?  Do I uninstall QB Enterprise on my computer and re-install?  I did uninstall the QODBC and then re-install the "correct one" earlier - was there a flag set in the registry that does not get "undone" when I uninstalled everything....

It sound like the problem is that I installed the QODBC Read only from the Enterprise system (if you can believe it I did this to see if I could activate later on so I could see if I could install this on client computers later!) - but never thought it was a problem when the ABOUT lists the serial number and says READ/WRITE.

Does this mean if a customer uses the read only no charge version of QODBC, then buys a key from us, and we activate, it wont work?

Thanks - Vic

1. Start QuickBooks
2. Open your company file, using the "File" menu, "Switch to Single-User Mode" (if you're running your company file in multi-user mode).
3. Edit/Preferences/Integrated applications...
4. Remove all "Flexquarters QODBC" records 
5. Close the preferences dialogs
6. Connect QODBC using VB Demo and the full version of QODBC. When QODBC starts, QuickBooks will again ask you permission for this driver to access your QuickBooks data. Check the "Allow this application to access NI or Social Security Numbers, customer credit card information, and other personal data" options and answer "Yes, Always” to this and the QODBC driver is added to the Integrated Application list.

   

   If you're using QuickBooks 2006 or 2007 in multi-user mode, you can also select the user account QODBC could use, but for unattended mode you must select QuickBooks "Admin" account:-

   

    

   Confirm that you want to allow this access by clicking on "Yes". This will allow applications to integrate with QuickBooks data when QuickBooks is running on the desktop.

    

7. Close all applications using QODBC and make sure all the connections are closed.

I've actually done all that and it still will not write - I deleted each entry in the integrated application, and then I re-started.

Does uninstalling QB Enterprise make any sense?  What is the code that sets this activation to read/write?

Any other odeas on how to fix this on my computer short of having me reformat (again) using Vista (hooray for MS!)

Vic

I have already read that post.

I am running as a standard user - have been able to run this program in Vista and Enterprise before, and have tried to elevate but that of course did not work either.  Interestingly, when I run my program it asks me 5 times to enter a login ID for the program FQQBSAV.exe - when I enter the standard user name and password - I get a message box that says "This program needs to be operated in elevated mode" - when I enter the administrator as part of this UOC process, it does not give me the message box - but still does not work telling me I need DESKTOP activation.

Can you review the updates made to 7.000214 - in particuliar the readme files says "the Vista License issue with activation" has been fixed - is it possible that this "problem" still exists or is made to not work with some new service pack.

Again, I respectivaly ask for an earlier release I can try to download and see if this fixes the problem.

Again, I have totally uninstalled the QODBC and re-installed with the FULL version - is it possible to get "full removal instructions" for this product as perhaps there is more to do than uninstalling, and deleteing the QODBC directory.

Thanks for your help - I have studied the forum for an answer and tried many things listed on your site - I still think there is an activation issue with your driver using Vista and SP1 - please prove me wrong and help me get this working.

Victor

I am using QB Version 7.0.  I have an activation key that works with 10 computers because it is an OEM version.  Therefore I have reloaded another computer in the same manner, using all the same releases as my existing computer, and the QODBC works great on this newly loaded computer.  There appears to be the same versions on both computers.

The only difference is I may have 'originally' downloaded a 'stripped' version of the product by initially downloading from the QB Utilitlies menu.  I am not sure why I did this - probably because I am a developer and wanted to see it work for my customers by using that utility from QB.

At any rate, I have completly uninstalled the QODBC but it appears not to completly uninstall with the control panel, install.log, by deleting all the QODBC dll I can find in the windows and subdirectories, uninstalling the DNS on my ODBC admin screen, then deleting the whole QODBC driver, and all the downloads I ever made with this product.

I then went into the registry and deleted 4 entries for QODBC.  Have I missed anything?

I then ran a program given to me to "uninstall" the QODBC licenses - and have ran that again uninstalling everything when I was done.

Then I reloaded (from scratch I was hoping) - everything that I deleted, and reconfigured the QODBC on my computer, the same way I have done dozens of times before and made it work on Vista on the first try - I understand the UOC functions, and program with the QB SDK daily - I understand those issues.

Then I ran the VBDEMO, as well as my VS 2005 program, and some ACCESS and Excel as well - all to get one field to update in my database.  Again, I get the same error:

Desktop Activation needed.

Today I renamed a license file I have never seen called I9K4UQLW.ocx - but it was re-created once I did the 'update' and got this desktop activation error.

Tom - someone at QODBC knows why this error checking in your system - it has to be a file, or a registry setting, or something - and I want to delete that one file - what is the name of this file.

It appears that I am being encouraged to just 'reformat' my computer - which I know will fix the problem as proven on a duplicate production computer - but this is a developement computer I am working on so imagine the hours downloading the service packs, SQL links, and other items.   This computer works great, I just cant do any QODBC developement on it.

But the QB SDK is working great, so I am trying my best not to just convert everything over to that platform and stop using your product - I want to use your product!

Again, TOM, What is the COMPLETE instructions to delete everything from my computer that responds to QODBC - have I forgot anything to delete?

The concepts this is a problem with license keys, certain releases, or other issues cannot be explained when the same duplicate computer has been rebuilt with all the same CD's and it works fine with QODBC and does not give this error.

The only help, again, I can give you is that I made the 'mistake' by originally downloaded the QB version of the QODBC driver (ORIGINALLY - not installed NOW) - and somehow that version does not completly uninstall correctly so you can then go and use the 'write' version afterwards.

Is this true the above sentence that once you download the QB QODBC utility from the Enterprise program version 7.0 you can not 'ACTIVATE' it!

HELP ME PLEASE with better answers. 

Vic

PS - I have spent hours reviewing all the entries on this matter in your forum and have tried EVERYTHING!  There is a file name - please help me!

When your QuickBooks Enterprise company file was accessed using the FREE QODBC Enterprise Edition (that doesn't require a CD Key), your company file became hard wired as read only access. This is under strict instructions from Intuit.

You will need to remove all the "Flexquarters QODBC" records in the Edit/Preferences/Integrated applications... options in QuickBooks Enterprise 7.0 for the company file.

Tom - I have already unistalled those licenses - and reinstalled them - the certificates to QB - however how do you explain another computer with the same configuration reading/writing to that same company file?  Therefore your idea does not make sense - but here is what I did today in desperation.

took off all the licenses and deactivated - removed QODBC and QB - removed all QB and QOBC and some FQB files related to your product.

Went thru the registry manually and removed all QB and QODBC references.  Deleted the license files in windows\system32

Now I will reload - I am still curious why you do not have a manual uninstall of the product which identifes the files affected for me to 'reference'  - can you please answer this question?  Is the information propreitary and I am not allowed to know it?  Do you simply not know what files you add to a system during an update?  Do you have a sample install.log?  You seem to avoid this basic question I am asking on every one of your responses but I dont know why so I get frusterated reading your answers that dont answer this question.

Thanks - Vic

The QODBC install log can be found in c:\Program Files\QODBC Driver for QuickBooks and clearly shows the files and registry keys installed by the QODBC installation. The operation of the registration system remains propreitary.

Thanks - of course now I have deleted the directories -

Understanding the registration systems remain propreitary - is there a way to list the files it creates so i can delete them too>....

I am getting desperate while at the same time willing to try anything short of formatting my disk to try again.

I must be close.

Thanks

Vic