On Apr 18, 2:11=A0pm, David Phillip Oster <os...@[EMAIL PROTECTED]
> wrote:
> No, this is a programming question. Unless you are familiar with the
> techniques for preserving consistency in a distributed database
> (multiple concurrent access over unreliable connections) you will have
> data corruption, whether it is a Windows only system or a mixed system.
I am. However, I also know that if the platform my code runs on has
issues/bugs, then my code will not work. For example, there are
plenty of bugs in SMB when a Windows XP PC connects to a Windows 98
file share. There are also bugs when using the IPX protocol between
certain versions of Windows PCs, especially if Norton anti-virus is
installed and not configured correctly (this was years ago that I
found these issues, so they may be fixed by now, not sure). Microsoft
still recommends you disable op****tunistic locking when using MS
Access under certain conditions (also due to bugs, although they don't
call them "bugs"). Windows Vista had/has bugs in the new SMB 2.0 they
added, which may have been fixed in SP1.
I know Mac OS has had some bugs in SMB also, with certain releases...
but sometimes even if all "bugs" have been fixed, you run across other
items that just don't work, but then find out it is "by design". For
example, in programming terms, it is possible for fcntl to return
ENOTSUP for a F_SETLK command... am I going to run in to that with
certain "conflicts" or "limited" platform sup****t in a mixed network
environment?
>
> (While there is no Micorosft Access, there is
> /Applications/Utilities/ODBC Administrator, so a Mac user could install
> an ODBC driver so a Mac application could manipulate a database hosted
> on Windows.)
Good to know -- now if I only knew if people were actually using this
on a regular basis and how well it really worked with concurrent and
heavy access.
|
