Don't know what I did but, I did something wrong. I created a new temporary database so I could restore an old database file to check finformation. The information did not restore so I decided to delete the temp database. When I tried to open the file to delete I get this message: Error # -64 Error #. 90615 File found erroropening file file4open C:\programfiles\parsonstechnology\familyorigin\Smithp.dbf click o.k. Error # -935 Error # 94001 Null infput parameter unexpected d4file click o.k. Program error exiting application Please help and I promise I will never do that again. I am using Ver 9.02 thanks in advance for any help Barb

Chabar59@aol.com wrote: >I created a new temporary database so I could restore an old database file to >check finformation. The information did not restore so I decided to delete >the temp database. When I tried to open the file to delete I get this message: > > Error # -64 . . . . . You don't need a new database to restore into. When you restore a backed up database, it creates anew, the database that was backed up and it will have the same name it had originally. Or it will over-write and replace the existing database you may still have with the same name. The name of the database is contained within the backup file and you cannot change that until after it is restored. If you want to look at an old version of your existing database without destroying your existing database then you must restore it to a different folder. So the database you restored may have restored OK and it just has a different name than you expected (it's original name). But none of that should have caused your new temporary database to go bad. I don't know what caused that. You may have to use windows explorer to delete all 35 files that make up that database in order to get rid of it. Perhaps an easier method to do that would be a procedure like this: 1. Create still another new database with the same name as the problem db in a different folder. 2. Backup the new, empty database and then delete it. 3. Restore the new database to the folder where the problem db is so that it over-writes and replaces the bad database. 4. Now you can open the newly restored db in FO and delete it too. Wayne League