|
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
|
|
| Access to Time Tracking table |
| Author |
Message |
|
|
| Posted : 2006-08-24 03:27:32 |
I have installed the latest version of QODBC and linked the Emplopyee and TimeTracking tables into an Access database. It appears to work fine. However in QB I can run a report that shows Timetracking records for employees in the week of July 30 - Aug 5 (report = Time by Name). When I look into the table from the Access side I can find only 2 records for that week for all employees and there should be many other records. I am using TxnDate as the selector. When I check on other weeks they seem to balance perfectly.
Is there another table I should be looking at or is there something else I am doing wrong? . |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-08-24 10:41:43 |
|
|
|
|
|
| Posted : 2006-08-25 04:06:02 |
Tom
Many thanks for the reply. I tried running the import from QB into Access without using the Optimizer and it did not change the results. I turned off the Optimizer in the setup screen. Should I have resynched the tables anyway?
What I find very strange is that QB can show me the data for the week in question but Access (the version is 2000) cannot. Most other (but not all) weeks are fine and balance perfectly. It seems to be a random event.
Would a pass through report solve this problem? If so then each time I run it I need all time cards (?timetracking records) from the beginning of the year with the fields: TxnID, TxnDate, EntityRefListID, ItemServiceRefFullName, DurationMinutes.
What we are doing is measuring productivity rates for the various employees which is why I need all Time cards each time in case they retroactively change the Item Service code on a given record.
Peter |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-08-25 13:25:12 |
| As you already connected the tables in MS Access, the table connections will still use the optimizer. So you still need to fully resync your TimeTracking table by running:
sp_optimizefullsync TimeTracking
Please use VB Demo to run the sp_optimizefullsync stored procedure and to re-run quires for the missing period in VB Demo. |
|
|
|
|