Issue with replacing a deleted file by renaming in Access

Dragon2000 · Post by **Dragon2000** » Wed Nov 15, 2006 4:24 am

I know you don't support Access. Personally I think you should because
a) it works
b) your product and sourcesafe are the only onces I can find that support sharing items between databases. And your product is a lot more reliable than sourcesafe.

Anyway, if you ever change your minds there's a slight issue you might want to be aware of that also affects Starteam and Perforce but not Sourcesafe.

If you delete an item in Access and then rename an item so it has the same name as the deleted item then it renames it successfully in Access but fails to rename it in sourcegear. However exiting Access between the delete and rename operation allows it to work corrrerctly. As does replacing a deleted item by drag and dropping from an external database. Considering the other SCC programs are affected I assume its actually an Access bug that sourcesafe has a workaround for but thought you might want to be aware.

lbauer · Post by **lbauer** » Wed Nov 15, 2006 10:37 am

Thanks for the report. It might be of interest to other users who are trying to use Vault with Access.

Dragon2000 · Post by **Dragon2000** » Tue Feb 06, 2007 9:13 am

Another renaming issue - you cannot rename a table. It comes back with the error 'The new name cannot be used because an object with that name already exists in Sourcegear Vault.'

I assume this has something to do with how Access supports SCC. It exports each form and query as a text file and adds them to source code control as individual files.

However the tables are exported as one single file for all the tables. This file has the name databasename.ACB. So what I assume is happening is that after the table rename, SCC is checking the name I've ended up with without realising that from its point of view I haven't actually renamed anything. The file that SCC needs to worry about remains as databasename.ACB and it's panicing because this name already exists.

So my question is this: is it Access performing the rename check or Sourcegear Vault? If Sourcegear - is there a way to disable this check?

lbauer · Post by **lbauer** » Wed Feb 07, 2007 12:54 pm

It might be Vault, thinking there's another object with the same name. But since we haven't tested Vault with Access and don't support it, it's just a guess.