Please review the QODBC message log for the SQL statement with the syntax error in it and advise.

Sorry, this is plain nonsense:

select * from Bill where 1 = 2

There's no column called 1 and 1 would never equal 2. What is generated this SQL Statement? The statement should just be:

select * from Bill

Your setup of the Enterprise company file just hasn't be configured for unattended mode access, see: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running? 

As far as using Alpha Five, please see the Alpha Five documentation or contact Alpha Five support.

If unattended mode doesn't work, then you need to follow the procedure at: After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works? 

QODBC is a ODBC driver that can be used by lots of programming languages (including Visual FoxPro and Alpha Five) and many applications. I suggest you use VB Demo and run:

select * from Bill

with the Enterprise company file to check that you don't have a corrupted company file first.

See: How do I use the VB Demo for testing? 

I'm going to guess that you have lots of bills in your big company file. Let's try getting it down to a smaller record set:

select * from Bill UNOPTIMIZED WHERE Txndate > {d '2007-01-31'} and Txndate < {d '2007-02-12'}

The hour glass means it's working on lots of data, this query limits the billing data to this month only. Let me know how it goes.

Because your company file is large, you need to increase your "Use Iterator or Chunk Size" setting from 500 to 20,000.

Iterator or Chunk Size determines the size of the rowsets that are retrieved from QuickBooks per fetch. Set this value high if you are exporting records from QuickBooks. The maximum Iterator or Chunk size that can be set is 100,000 (higher than that and it resets itself back to the default of 500).

The real way to do this is to first optimize your tables by using the [ Load Updated Data ] or [ Reload All Data ] (if you have just started using QODBC) option in the QODBC setup screen.

Once optimization is completed (the time this takes is dependent on the size of your company file), use queries with the NOSYNC command to import the tables into Alpha Five like this for each of the tables you wish to import:

select * from Bill NOSYNC
select * from BillItemLine NOSYNC
select * from BillExpenseLine NOSYNC

If you're only interested in some of the tables, you can instead only optimize selected tables by running:-

sp_optimizefullsync Bill

and then update it manually at any point of time by doing:-

sp_optimizeupdatesync Bill

Because QODBC can optimizer your data and automatically update it for you, most of the time it's better to call the optimized tables instead of importing the data in the first place. See: How do I setup the QODBC Optimizer? Where are the Optimizer options? for more.