When I am defining the data source in the  ODBC Admin panel I get the error that pops up a redirect to your support web site.

If I look in the messages tab and look at the review ODBC messages button I see;

2007-06-08 14:43:23 QODBC Ver:  7.00.00.214 *********************************************************************************************************************
IsAService: False
Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040430, This application is unable to log into this QuickBooks company data file automatically. The QuickBooks administrator must grant permission for automatic login throug
h the Integrated Application preferences.  If such permission was already granted, the administrator must revoke permission, save preferences, then grant the permission again.
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"

The problem is that Quickbooks PRO 2007 does not pop up the window to allow access to the company file. The admin has reviewed the Integrated Application preferences window and does not see anything that would be stopping it. Is there another possible setup error that would be not allowing this window to pop up? Is there a manual way to force the access?

I have performed the procedure mentioned earlier and I have been successful in logging on in "unattended" mode. Now when I have a user logged on the the admin id and I attempt to access the database I get the following error 80040435.

This lead me to a post by a Thomas McKane and full circle back to the fix for unattended mode. It seems that the error comes into play when a session other than the one that is controlled by my user id is attempting to access the database. Is there an inherent  problem with this? If so your product is going to be very difficult for us to use. I will try again after everyone has logged off the database again this evening to verify I can still access the data with no one logged in .

The solution mentioned in ;

http://www.qdeveloper.com.au/forum.php?homeinclude=topicdetails&forum_id=1&category_id=19&post_id=303

refered to doing step 17 again which is to run the application in unattended mode.  Is there a special setup option in the Qodbc setup? If the Qodbc setup screen displayed  with it is all that is required to do this I have done that.

Also the second solution (post id=303) is refering to V6 of Quickbooks (2006 ?) I am running 2007. If so your version for 2007 has inherited the same problem.

To rectify your problem, please do the full 17 step procedure outlined in the original post at: After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works?  and use VB Demo and a normal DSN connection to correct the QuickBooks auto-login connection first with the other users on the network.

You will need to remove all QuickBooks user accounts for the company file.

This is a known problem that exists in the QuickBooks qbXML SDK from Intuit, caused by QuickBooks when upgrading an existing QuickBooks company file to the new 2006 (or 2007) USA format or even adding new user accounts to QuickBooks 2006 or 2007. 

This isn't a fault within QODBC.

Tom,

Thanks for your patience.

I can only assume that you are calling step 17 the following;

1. Run the application in unattended mode 

If Unattended mode still does not work  
Remove the QODBC integrated application entries from the original QuickBooks 2003/2004/2005 company file, then allow QuickBooks 2006 (or 2007) to upgrade the company file to the new format and then have your applications connect the company files with QuickBooks and the company file open to set up the integrated application options again.

 If that is indeed true then I have to ask you to read my post....

This is a from scratch installation of Quickbooks Pro 2007. There are no "other Qodbc applications to remove". The ones in Quickbooks 2007 are the only ones that have ever been made. There is no Company file to allow 2007 to upgrade to a new format. Your answer does not apply to our situation.

If you are willing I can setup a time when you can talk with me.  if I have to stay late so be it. Are you GMT+10 +9:30 +9 or +8 ? TIA. 

--
Larry Machin
Senior Software Engineer
Secure64 Software Corporation
5600 S. Quebec St., Ste 320D,
Greenwood Village, CO 80111
Phone: (303) 242-5898
FAX: (720) 489-0694

Repeat, you need to do ALL 17 steps (not just step 17) which means you will need to remove all QuickBooks user acounts, remove all FLEXquarters QODBC integrated applications, then re-add all QuickBooks user accounts, and then reconnect QODBC logged in as the QuickBooks "Admin" account using the disired user account on each users copy of QuickBooks on their computer.

When new QuickBooks user accounts are added to QuickBooks 2006 or 2007 company files, a "Intuit" bug within QuickBooks sometimes breaks unattended access. This applies to both upgrades and new installations alike. If you add a new QuickBooks user next month, unattended access may be broken yet, again.