From: alleyhouse@hetnet.nl   
      
   Kenneth,   
      
   Since you went back to a system-image of a time when all worked fine,   
   you should not be dealing with a paradox, bde or windows problem. The   
   logical conclusion would be, that you are either dealing with a hardware   
   problem in either the PC itself or it's connection to the network.   
      
   But a problem in that area, that only influences 1 form seems rather   
   unlikely. Unless there is something special about that form, that makes   
   it trigger the problem, where the others don't. So is there anything   
   specific about that form, that really makes it stand out from the   
   others? Does it access local- and/or network files or tables, that the   
   other forms don't? Does it access a larger number of tables; is it much   
   larger in size; does it use libraries, that the others don't; etc.   
      
   If such things are not the case, then a hardware problem remains rather   
   unlikely. Then the next best place to look, would be the server or   
   networksettings; could there be anything on there, that restrict this   
   specific PC in a way that the other PC's are not restricted?   
      
   Kind regards   
   Jan Stegehuis   
      
      
   Kenneth schreef:   
   > Hi Tony,   
   >   
   > Please see my responses inline below...   
   >   
   >   
   > On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"   
   >  wrote:   
   >   
   >> P9...   
   >>   
   >> Full or Runtime?   
   >   
   > Full version.   
   >   
   >> What minor version, and is the version the exact same for both   
   >> systems?   
   >   
   > I will have that in the morning, but I am quite certain that   
   > the versions are exactly the same on all boxes.   
   >   
   >> "All of a sudden" usually points to a Windows update, in my   
   >> experience.   
   >>   
   >> Or to a software install that should be totally innocuous, but which   
   >> kills something within Paradox.   
   >   
   > There were no modifications of the faulty system (in either   
   > sense you describe.) Also, we image these systems frequently   
   > and have returned to an image that was created when the   
   > system had a clean installation of Windows about two months   
   > ago. That image ran the Paradox form perfectly for those   
   > many weeks. Now, having gone back to that image, we have the   
   > problem.   
   >   
   >> Or even a new printer installed on the problem system.   
   >   
   > Nope... Nothing new on the hardware side.   
   >> Does the operator of the problem system play games on the computer?   
   >>   
   >   
   > No games at all.   
   >   
   >> I think you said the form resides on the server.  Does it (the form)   
   >> USE libraries or any other file type that are local to each computer?   
   >   
   > The BDE configuration is local...   
   >   
   > The form uses nothing that is local. All tables, libraries,   
   > etc. are on the server. (This is, by the way, a "nominal"   
   > server in that it also runs a non-server version of Windows   
   > (I believe 2000 Pro) on our peer to peer lan of six boxes.   
   > The "server" is not used as a workstation.   
   >   
   > All that said, is there any chance that flaky memory on the   
   > problem system could cause the problem I have described?   
   >   
   > I am currently running Memtest+ and by morning it will have   
   > about 15 hours on the clock, but at last check, it shows no   
   > errors.   
   >   
   > Thanks for any further help,   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)