Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Approach 97 on Windows XP error 1

Status
Not open for further replies.

growntree

Technical User
Feb 7, 2002
3
GB
I am using Approach 97 on XP Pro and whilst it seems to work fine, a particular file that can be opened on NT PCs with exactly the same version of approach, returns the following error on my XP PC:

Couldn't open database [dbf file] because it is damaged.

The error message box also displays the buttons OK and Help. (I've put [dbf file] in the error message as it's about a 30 character path for the actual file name)
The file I am trying to open is an APR file, but it seems to reference this DBF file. Approach is installed in exactly the same place off the C drive as it is on the NT PCs. I have since put SP1 on XP which has made no difference to this problem.

Cheers in advance for any help

Graham
 
No, it won't open in XP, it still says it is damaged. It will open on an NT PC. The file is stored on the network, so it is exactly the same copy in both cases.
 
Then it looks like a problem with XP. I had a similar problem a few days ago after installing SP1 on a workstation. I was getting bogus "access denied" messages opening files (on NT4 and W2000 servers) from a number of different apps and most attempts to save a file failed too.

Had to format the hard drive and reinstall XP Pro to get rid of the service pack. Everything's working normally again now.

Paul Bent
Northwind IT Systems
 
I was experiencing the same problem with one of my workstations. I was able to access a database stored on a Novell server with two Windows XP workstations, but a third XP workstation was giving the error the database file was damaged.
In this instance, it turned out to be someone had installed the latest Novell client on that workstation. The other two workstations were using the Windows client. Removing the Novell client from the affected workstation allowed the workstation to access the shared database again.
I'm not sure what your environment is like, but thought I would share what I found with a very similar problem.
 
r1100rider
Did you mean the two machines that could access the shared database were using a Windows 98 client from Novell instead of the XP client from Novell?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top