From: Craig B. <cr...@bo...> - 2003-09-09 23:03:07
|
> Maybe Pilot-DB is looking for a file that is no longer there. The error message sort of gave that impression, yes... > That > is, maybe you deleted a DB file, but Pilot-DB thinks it is still > there. Try opening your DBs one by one. If you can't open one of > them, then delete it (which will actually only remove it's name > from the list of DBs, since it's not there anyway). I've seen that when a VFS based database is open and the device fatal exceptions. But the result has always been a visible database duplication (up to now). One copy would open and the other wouldn't and could be deleted. Not the case here. I was merely fishing for some thoughts from developers as to where to look from there insight into the code, since this was the first I'd seen the issue, and I have about 40 databases, so opening all was a bit tedious. But that's in fact what I ended up doing. First Deleting DBDatabases, lost categorization as expected, but also didn't remove the error on launch. So I restored it from SD Backup. I launched each database in turn, and especially checked each database with links to other databases via Edit Database Design, and with a new test record to insure the links were all valid. I got to the end without discovering any issues. All databases and links opened fine. Yet that resolved the issue somehow. There's no longer the error message on Pilot-db launch. Bandaid on the symptom, but failed to glean knowledge as to the source. |