|
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
|
|
| QUERY DOES NOT MATCH QB REPORT |
| Author |
Message |
|
|
| Posted : 2008-04-04 03:10:13 |
I am running the following query,
select TxnID, TxnDate, EntityRefListID, CustomerRefListID, ItemServiceRefListID, DurationMinutes From TimeTracking Where (TxnDate <= {d'2006-01-31'} AND TxnDate >= {d'2006-01-01'})
7 rows are returned that are 3569.2 hours short of the equivalent report pulled in QB. What am I missing here? I am really panicing at the moment. Any help would be greatly appreciated.
Thanks,
Cam "Icabod" Taylor |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-04-04 07:48:24 |
Try running:
select TxnID, TxnDate, EntityRefListID, CustomerRefListID, ItemServiceRefListID,
DurationMinutes From TimeTracking UNOPTIMIZED
Where TxnDate >= {d'2006-01-01'}
and TxnDate <= {d'2006-01-31'}
if that's correct, repair your optimized file by running:
sp_optimizefullsync TimeTracking
For more on how to use the optimizer see: How do I setup the QODBC Optimizer? Where are the Optimizer options? |
|
|
|
|
|
| Posted : 2008-04-04 09:06:52 |
Thanks for the reply Tom. I actually just configured without the optimizer, and got the effect I planned. It isn't a major issue with my application, so it works out. I have to say I'm foggy about the work of the optimizer, but not using it at all seems to be my best bet at the moment.
Thanks. |
|
|
|
|