dfenton
AWF VIP
- Local time
- Today, 13:57
- Joined
- May 22, 2007
- Messages
- 469
agree but if the users dont have access what can I do. The current mode is they use a word doc. that gets handed back and forth until its complete. Once its complete they turn it in and someone in the office that has a connection enters that data into a database. This process works but its not very efficient and we lose data and end up with incomplete records. So to simplify a bit I thought I could have the user start a checklist complete as much as they can before they day ends then do a data dump the user 2 and so on until its complete.Once complete the data could then be loaded into the main table but not until it was complete.
When you say "users don't have access" do you mean network access or MS Access? If the latter, they don't need it. If you install the TSI Synchronizer, you can synch direct via a vbScript like this:
Code:
Dim tsiSynch
Set tsiSynch = CreateObject("Synch40.Synchronizer")
tsiSynch.Running = True
tsiSynch.UID = "Admin"
tsiSynch.Password = "..."
tsiSynch.DatabaseName = "E:\ClientReplicas\RepTest\wtsDataHub.mdb"
tsiSynch.SynchDirect "\\Server\Databases\wtsData.mdb"
msgbox "Finished Synchronization!"
tsiSynch.Running = False
Set tsiSynch = Nothing
Since Jet is installed on every copy of Windows starting with Windows 2000, this should work just fine once the Jet synchronizer has been run once and the TSI Synchronizer registered.
You can get the Jet synchronizer by running this Jet update:
http://support.microsoft.com/kb/321076/en-us
To initialize it, just run mstran40.exe, which is one of the files that is put on your machine when you run the update. The standard location that it will get installed in is:
%ProgramFiles%\Common Files\Microsoft Shared\Replication Manager 4.0
You can get the TSI Synchronizer here:
http://trigeminal.com/lang/1033/utility.asp?ItemID=9#9
To initialize it you can use regsvr32 or just use Access to register it by adding it as a reference in a database (after which you can remove the reference).
Once you've done that, the vbScript should run just fine, as long as provide it with the correct replica names.
Alternatively, you could program the whole thing in Word itself and provide a toolbar button to do the synch. The code would be almost identical as vbScript is quite close to actual VBA, but since I never program in Word, I can't say if it will run without change.