E
Eric
I've just been sitting around watching the clock and waiting for them
to ever post an update to this. Does anyone have any inside knowledge
on this, and maybe can tell me if they ever plan to update this issue?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216#12
In this article Microsoft says:
---------------------------
If you can, do not share a Microsoft Jet database file that is stored
on a Microsoft Windows 95, a Microsoft Windows 98, or a Microsoft
Windows Millennium Edition (Me) file share with Windows NT or Windows
2000 clients. When you have a mixture of computers on a network with
some computers running Windows 95, Windows 98, or Windows Me and some
running Windows NT or Windows 2000, and you have to share the database
with other network users, Microsoft recommends that you store and
share the database file on a Windows NT or Windows 2000 server with
opportunistic locking disabled. Corruption can occur if you have
Windows NT or Windows 2000 client computers share a file that is
stored on a Windows 95, a Windows 98, or a Windows Me file share. This
can occur even if the Windows NT or Windows 2000 client have
opportunistic locking disabled. This issue is still under
investigation, and Microsoft will post further information to this
article when it becomes available.
--------------------------
I'm mostly wondering about this part "This issue is still under
investigation, and Microsoft will post further information to this
article when it becomes available."
I'm sure they aren't investigating it still, no way they would spend
this much money (time is money) on an issue. So I'm sure they have
stopped, and probably never found an answer. Can they at least post
an update and admit that they have stopped looking and will never find
an answer? Of course not, because then they would have to start
saying XP isn't compatible with 98 (and other combos), and sales would
go down.
Sorry for the flame, but I'm getting sick and tired of dealing with
this issue, which IS a major issue for anyone spending $$$ due to data
corruption, and not everyone can just convert over to a client/server
model (MSDE or SQL) like they suggest. It also costs big $$$ to move
server to the XP machine, more $$ for MS, so that isn't an option
either.
to ever post an update to this. Does anyone have any inside knowledge
on this, and maybe can tell me if they ever plan to update this issue?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300216#12
In this article Microsoft says:
---------------------------
If you can, do not share a Microsoft Jet database file that is stored
on a Microsoft Windows 95, a Microsoft Windows 98, or a Microsoft
Windows Millennium Edition (Me) file share with Windows NT or Windows
2000 clients. When you have a mixture of computers on a network with
some computers running Windows 95, Windows 98, or Windows Me and some
running Windows NT or Windows 2000, and you have to share the database
with other network users, Microsoft recommends that you store and
share the database file on a Windows NT or Windows 2000 server with
opportunistic locking disabled. Corruption can occur if you have
Windows NT or Windows 2000 client computers share a file that is
stored on a Windows 95, a Windows 98, or a Windows Me file share. This
can occur even if the Windows NT or Windows 2000 client have
opportunistic locking disabled. This issue is still under
investigation, and Microsoft will post further information to this
article when it becomes available.
--------------------------
I'm mostly wondering about this part "This issue is still under
investigation, and Microsoft will post further information to this
article when it becomes available."
I'm sure they aren't investigating it still, no way they would spend
this much money (time is money) on an issue. So I'm sure they have
stopped, and probably never found an answer. Can they at least post
an update and admit that they have stopped looking and will never find
an answer? Of course not, because then they would have to start
saying XP isn't compatible with 98 (and other combos), and sales would
go down.
Sorry for the flame, but I'm getting sick and tired of dealing with
this issue, which IS a major issue for anyone spending $$$ due to data
corruption, and not everyone can just convert over to a client/server
model (MSDE or SQL) like they suggest. It also costs big $$$ to move
server to the XP machine, more $$ for MS, so that isn't an option
either.