|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| Issue with Queries on TimeTracking table |
| Author |
Message |
|
|
| Posted : 2008-06-19 00:50:08 |
I am seeing some invalid results on queries on time tracking table. For example when I do a "time by name only" (for previous month) report in Quickbooks and do a similar query in QODBC (using access) for one employee (out of about 40) I get incorrect results (time short by 24 hours). When I do a detailed query I see that for that employee QODBC is not getting data for the first 3 days of the month.
A few weeks ago I was doing another query to calculate Vacation used and there it seemed like QODBC was getting double records for Some employees for a particular month (so their vacation time was inflated, but again this was not happening for everyone). In that case it seemed like (and I could be wrong) that QODBC was getiing TimeTracking records that had (possibily) been deleted in QBs (as for these employees I think I had deleted some time data, including the vacation time, and reentered).
I am using QODBC version 8.00.00.242 and QB Pro 2007.
Any Ideas?
Thanks |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-06-19 07:52:15 |
Yes, deleted rows can still be in the optimized table image. If you are deleting and editing time sheets all the time, then I suggest you either rely on the TimeByName report or force a rebuild of the optimized TimeTracking by adding a VERIFY tag like this:
SELECT TxnDate as Date, ItemServiceRefFullName as Item,
IsBilled as "Billing Status", (DurationMinutes /60.00) as Hours
FROM TimeTracking verify
where EntityRefFullName = 'Dan T. Miller'
and CustomerRefFullName = 'Cook, Brian:Kitchen'
and TxnDate >= {d'2007-10-01'} and TxnDate <= {d'2007-12-15'}
You only need to do it once until you start deleting entries again.
See also:
How do I run a Time by Name Report?
Table Relations for TimeByName and TimeTracking
How do I setup the QODBC Optimizer? Where are the Optimizer options? |
|
|
|
|