Thanks,
John Jakus
You can syncronize with MS Access using SnapShot Connector (3:rd part driver). It uses a snapshot technology instead of monitoring triggers and supports both ODBC and LDAP databases. More information can be found at www.pulsen.com/xml.
Best regards,
Tobias L
>>> John Jakus<John.Jakus@*diespammerdie*Valence.com> 2004-01-27 00:22:17 >>>
It is a DirXML driver. All logics, schema mapping and rule management is done with DirXML.
Best regards,
Tobias L.
>>> John Jakus<John.Jakus@*diespammerdie*Valence.com> 2004-01-27 19:08:12 >>>
Thanks,
John Jakus
that's not surprising, since there is NO WAY to run MS Access databases (or,
more accurately, the JET engine) on non-Windows platforms.
> My
> Database for MS Access resides on the NetWare server so will I have to
> have a workstation logged into the NetWare server all the time to get
> this to work?
Yep, that's what you'll need to do. You could use CIFS on the NetWare server
if installing a NW client on the Windows server is not an option for you.
--
Jim
NSC SYsop
Cheers,
John Jakus
I understand the hesitation, but we do it all the time. Just create a
special user account with ONLY rights to the directory the MDB sits in. The
worse case with this setup is that the MDB could get deleted, which is no
different than if it were local on the windows box itself. I've got machines
that do similar things that stay logged in for months at a time. It's no big
deal ;-)
--
Jim
NSC SYsop
Cheers,
John Jakus
Heheheh.. strange, but true ;-) They can be remarkably stable when only
allowed to do one task!
--
Jim
NSC SYsop