Tabbles does not only use the file path to identify files, but also the volume serial number of the partition, and the partition size.

This is needed because 1) there must not be confusion if a drive changes letter, and 2) on the Cloud many users could have the same path for different files, so the file path is not enough.

For this reason, in order to move files across disks, you need to move them with either Explorer or Tabbles. Then, Tabbles will update its internal database with the new disk informations. If instead you copy the files, as you have done, nothing happens in Tabbles’ database, and afterwards there is no easy way to tell Tabbles that the file path is the same but the disk has changed.

Here’s what you can do:

1) redo the file move operation properly: if you still have the old disk, and the content of the files has not changed, connect the disk and move the files to the new disk (with explorer, or better with Tabbles).

2) otherwise you need to manually update the database, with the new disk id. You need to use Sql Management Studio and run a query I will give you. You also need to tell me the partition size of both the old disk and of the new disk, and the volume serial number of both the old disk and of the new disk. You can discover them as follows:

a) in Tabbles, locate a file with the “unplugged” icon, right-click the file, advanced > “see which disk contains this file”. tell me the data of the disk.

b) in Tabbles, right click on the new disk, in the side panel, folder-menu > advanced > see which disk contains this file, and tell me the info.

Hello,

I have exactly the same problem as the person who created this thread.

I am now unfortunately in need of the 2nd solution you have provided.

I have downloaded SQL Management Studio and these are the disk properties you were asking for.

Old Partition:

Volumer Serial: C2F453E8
Size: 833617915904

New Partition:

Volume Serial: 72DEEF70
Size: 989996249088

This is my tabbles version: 3.1.29 Portable

Thank you

Edit:

So with the information i had (having to replace the volume serial and size of the partition) i actually figured out a solution myself.

I exported my current database and replaced all instances of the old volume serial and size with the new ones in the exported xml file.

Then I deleted all my tabbles (to get rid of the faulty association) and then imported my modified xml file.

It worked 🙂

Glad you solved it yourself. We don’t quite remember how Tabbles 3 works anyway. 🙂