It should read:
"The bug does *not* occur when the database is served by Samba and the Office components for Access are on the local hard drive." I worked with Jeremy on this and we tried many combinations of implementations. We serve the entire Office suite (Office 2K and Office XP - on separate machines) from shares in accordance with the directions set forth by Microsoft. Both products exhibit the problem in Samba starting with 2.2.3. I am still compiling information for Jeremy on how to recreate the exact installation we have, but the solution for us right now was to set: nt status support = no and everything ran fine from that point forward. Thanks again, Jeremy! I will have the docs you need to recreate our installation next week. Bill On Fri, 3 May 2002, Konkol, Josh wrote: > In the Known Bugs section of the Release Notes, does it mean you can or > can't have the Access *.exe on the server. Does it work when the *.exe is > on the client ? > > Here's a snip from the Release Notes: > > Known Bugs > ---------- > > * Under certain conditions when serving the MS Access 2000 > executable file and an Access database from a Samba share, > it is possible to experience data corruption. This pug does > does occur when the database is served from a Samba file share > but the Access *.exe is stored on the client's local file system. > The exact reason for this bug is unknown at this time. > > > > > Josh Konkol, CNE MCSE > Senior Network Analyst > GuideOne Insurance > Mail Stop AB-1 > 515-267-2427 > [EMAIL PROTECTED] > > .~. > /V\ > /( )\ > ^^-^^ > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
