Author Topic: TP9 sql database  (Read 2717 times)

0 Members and 1 Guest are viewing this topic.

laknox

  • Member
  • **
  • Posts: 2
    • View Profile
TP9 sql database
« on: 2014-06-12 00:42:23 »
I have 2 databases; one with personal pictures and the other with business pictures.  Different names and pictures are stored on different drives.  The business pics are stored on a NAS.  I just had to change the password for accessing my NAS and now TP9 won't recognize that database.  Is there a way to enter the new info into the d.b. or do I have to delete it and start over?

Lyle

Daan van Rooijen

  • Administrator
  • Sr. Member
  • *****
  • Posts: 938
    • View Profile
TP9 sql database
« Reply #1 on: 2014-06-12 03:17:43 »
First, be sure that Auto Remove Orphans (Opt|Pref|Thumbnails) is off.

If other programs (eg Explorer) can access that drive, ThumbsPlus shouldn't have any trouble with it either. Are you sure that you did not also change the server name (of the NAS) or the volume label (of the drive in the NAS)? Either of those could cause TP to no longer recognize it, too. When you lookup the old entry for the NAS drive in your tree panel, you can right-click on it and select Volume Properties to see by what label that drive used to be known (if you want to restore that name, be sure to exit TP and do it using Explorer or some other tool. Then when you launch TP and it recognizes the drive again, you can use TP to change that label back to the desired new name, and at that point TP can update its own records so that it can continue to recognize the drive and its contents in the future).

See also Additional References > Database volume matching in the helpfile.

If this doesn't help, please let me know what kind of password you changed, and which application or part of Windows is asking for that password.
I'm volunteering as a moderator - I do not work for Cerious Software, Inc.

laknox

  • Member
  • **
  • Posts: 2
    • View Profile
TP9 sql database
« Reply #2 on: 2014-06-12 18:58:42 »
Working, now.  Seems a reboot and/or re-entering the p.w. solved the problem.  Thanks...