Cannot link or import timetracking table from Quickbooks |
Author |
Message |
|
Posted : 2008-08-30 05:11:51 |
I have been using QODBC for several links to different client Quickbooks databases. I am having a problem getting timetracking data from one Quickbooks database. I am assuming that the data is stored in the timetracking table, as I can see the data in "Time By Job Detail" reports. Is the time that is shown there always coming from the timetracking table? If so, I cannot import from this table. When it imports, I get the table with no records. Is it possible that this data is not stored in the timetracking table. Are employee hours against jobs stored in any other tables in Quickbooks? If not, what could be my problem? We are using the Enterprise version of Quickbooks 7.0 and I even downloaded and installed build231.exe. I am logging in through the ODBC using a user ID in Quickbooks that can see the time by job detail report, so I assume it has full rights. Any help would be most appreciated.
Bob |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2008-08-31 23:57:40 |
Try logging in as the QuickBooks "Admin" user and check again. Because your access was limited by the QuickBooks "User ID" account you used if the first place, the optimized table will not have been built correctly so you will need to force a rebuid by running:
SELECT * from TIMETRACKING Verify |
|
|
|
|
Posted : 2008-09-03 05:12:31 |
I tried logging in as ADMIN and using VBDemo32, ran the command:
SELECT * From TimeTracking Verify
It indicated Optimizing ... but returned no records.
Any other thoughts?
Thanks. |
|
|
|
|
Posted : 2008-09-03 06:01:49 |
Is it possible that because this Quickbooks database has such a large timetracking file, that there is a problem with the ODBC? Are there any settings that I can use to accomodate a very large timetracking table? I suspect that this is the problem.
Thanks. |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2008-09-03 07:41:11 |
|
|
|
|
Posted : 2008-09-03 22:29:04 |
I was able to select a small subset of the records from TimeTracking using this command. I was limited to 10,000 records using VBDemo. I suspect that this table has over half a million records in it. I cannot access it via the QODBC using MSAccess, even turning optimizing off. Is there a limitation on the table size for your ODBC? It appears to timeout after about 8 seconds and returns no records. Will I have to select 10,000 records at a time using VBDemo and cut those into a spreadsheet? Optimizing times out as well. Any thoughts would be much appreciated. I'm at a deadend with this database table.
Thanks. |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2008-09-04 07:45:30 |
|
|
|