Using Access 2000.
So I have read several pages about people getting the "Disk or Network Error". At least I am not the only one. One thing I just read though was a bit haunting. cichlid (user on this forum) said basically that Win2k can corrupt your Access database. I just fought tooth and nail to get my machine upgraded from 98 to 2k because I was having memory management problems, and Win2k was recommended and it did solve the problem. Now I read this and am very concerned.
So where do I go from here. Could my PC being Win2k cause this problem or is it only if the Back End on the network is Win2k? He/she did say that Microsoft was working on a fix, he/she wrote that a year ago and I can not find anything on Microsoft's website about it. Anyone know of a fix to the corruption or Win2k problem or where I could find white papers on it?
The application I am concerned about is not live yet so I can not say whether for sure users will get the "Disk or Network Error" or whether they will cause a corruption. All users have Win98. I get the error though especially when I either do mass updating or mass deleting of records. This happens whether I am in the Development front end or the Back End on the network.
The server the BE currently is on is not really a server but a computer from the stone age I think. PII 200MHZ maybe 128 ram, not sure could be 64. I am working on moving it to a more up to date server machine. But I did place it on a test server that is much better and the application seemed to be more responsive but I still would get this "Disk or Network Error."
I guess what I am asking is what would the people in the Access community suggest for the Server CPU specs (processor, ram, etc.) and Operating System (Win2k, NT, Win98). Unfortunately NT may not be an option because the company as a standard has been moving everything to Win2k. The data is pretty important to many people so I would likely get the backing to do what is necessary to insure the integrity but as I asked in the 2nd paragraph white papers or something like that would help with whatever my argument will be.
thanks for the ear.
e-train Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain
So I have read several pages about people getting the "Disk or Network Error". At least I am not the only one. One thing I just read though was a bit haunting. cichlid (user on this forum) said basically that Win2k can corrupt your Access database. I just fought tooth and nail to get my machine upgraded from 98 to 2k because I was having memory management problems, and Win2k was recommended and it did solve the problem. Now I read this and am very concerned.
So where do I go from here. Could my PC being Win2k cause this problem or is it only if the Back End on the network is Win2k? He/she did say that Microsoft was working on a fix, he/she wrote that a year ago and I can not find anything on Microsoft's website about it. Anyone know of a fix to the corruption or Win2k problem or where I could find white papers on it?
The application I am concerned about is not live yet so I can not say whether for sure users will get the "Disk or Network Error" or whether they will cause a corruption. All users have Win98. I get the error though especially when I either do mass updating or mass deleting of records. This happens whether I am in the Development front end or the Back End on the network.
The server the BE currently is on is not really a server but a computer from the stone age I think. PII 200MHZ maybe 128 ram, not sure could be 64. I am working on moving it to a more up to date server machine. But I did place it on a test server that is much better and the application seemed to be more responsive but I still would get this "Disk or Network Error."
I guess what I am asking is what would the people in the Access community suggest for the Server CPU specs (processor, ram, etc.) and Operating System (Win2k, NT, Win98). Unfortunately NT may not be an option because the company as a standard has been moving everything to Win2k. The data is pretty important to many people so I would likely get the backing to do what is necessary to insure the integrity but as I asked in the 2nd paragraph white papers or something like that would help with whatever my argument will be.
thanks for the ear.
e-train Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain