English > Support

File Scanner Causes Crash

<< < (2/4) > >>

rick.ca:
I hope you remembered the second rule—backup before downgrading. The file scanner works fine in v16. There's no point in reverting to v14.

Does the file scanner work with a new database connected to the server? Maybe the problem is with your database, not with it being connected to the server.

junk_struc:

rick, i think you are right, it is something in the database

if i start a new database (not connected to server or standalone) file scanner is fine.

if i then restore from a previous backup into this same blank file (only works if not connected to server), then the file scanner stops working and asks if i want to quit.

suggestions?

craig

rick.ca:
No, I meant you should create a new database—completely independent of the old—connect that to the server, and see if the file scanner works.

You can't restore a backup into a new database—it just opens the backup.

junk_struc:

see second sentence above (replace word if with when, poor grammar style).  yes when i create a new database and ask for a file scan, it starts without error.  this is an affirmative for both a standalone database and if i connect to server with a new database and do the same thing.

is there a way to get my existing (perhaps corrupt??) data into a new database?

craig

rick.ca:

--- Quote ---is there a way to get my existing (perhaps corrupt??) data into a new database?
--- End quote ---

Other than exporting an reimporting, no. Nostra may have suggestions after reviewing your bug report.

Navigation

[0] Message Index

[#] Next page

[*] Previous page