Can a TW database be moved to a different folder?

[rob2218]

Can a TW database or several of them, be selected and relocated to a different folder (as you can see they are out of the folder designated for them) without disrupting the flow of the project information?

I don't want to move these files from outside the folder they are suppose to be in if it's going to cause loss of linkages?

Please advise.

[Link]

I haven't tried it, but my experience with the TW database is to leave it well alone!! Manually moving these folders would almost certainly break the link between the database and ArchiCAD.

These are how the folders are designed to structured AFAIK - One folder per TW project. It's definitely how it looks here.

Why do you want to move them anyway, just to be tidy? There's no real need otherwise, as you never really need to see these files and folders because they are all accessed internally.

Cheers,
Link.

[Karl Ottenstein]

Beyond Link's wise remarks... it appears that you've told the server to store your TW projects in the same folder ("CURRENT PROJECTS") as your solo projects? If that's the case, I don't think it is a good idea, or useful for that matter, as the TW data files are not of any use other than via the BIM Server. You cannot open and use them in any ordinary way.

Cheers,
Karl

[Link]

Yes, I noticed that too Karl. It's a good point to raise.

Solo Projects and TW2 database information should be kept completely separate IMO. Otherwise you're playing with fire, all it takes is one accidental delete and you could have numerous corruptions. There's not many TW projects in there as of yet. If it were me, I would have everyone leave the projects (sending all changes), save all files as solo projects, delete them from the BIM Server, redirect your Projects folder (and probably your library folder too), then re-share all the projects on the BIM Server. You may have to re-link any hotlinked modules, but I'd ask GS for confirmation on that if it is an issue.

There may seem like easier ways but that's by far the safest way. Could be a late night, but then you'll be off to a fresh start. Just make sure your chosen drive has plenty of room on it, as the database files bloat enormously.

Cheers,
Link.

[rob2218]

Along the lines of accidental deletes......so, where exactly would a PLN copy of the TW database be located on my hard drive?
What folder should I look for?

Where in the Archicad program does it state where a PLN copy is saved to incase something where to happen to the database file?

[Link]

There is no pln. Simple as that.

Cheers,
Link.

[rob2218]

But......the install says it saves a local copy on your hard drive.....so incase you got disconnected or traveled....you could always have a PLN as the backup???

[Link]

rob2218 wrote:
But......the install says it saves a local copy on your hard drive.....so incase you got disconnected or traveled....you could always have a PLN as the backup???

It saves a local copy, but not a PLN. Check your Work Environment> Company Standards Schemes> Special Folders> Teamwork Data Folder. This is where the local drafts are stored on your computer. You can navigate to it in your OS. On a PC it will default to C:\Users\<username>\Graphisoft\TW Data.

All you will find is the same kind of database gobbily-gook that you see on your BIM Server. This local data is what the TW2 Database links and compares the delta changes to, all within ArchiCAD. And you can work on it offline and even save it as a PLN if you need to, but none of it can be used on it's own. (Actually in an emergency you can rename the @Global.T file to a PLN and retrieve some model data but you'd have to be pretty desperate).

That's why in my related post, I suggest a good backup or disaster recovery plan. All this TW2 has made it much easier for users to collaborate but it's made it more challenging for those of us who must manage it.

Cheers,
Link.

[rob2218]

I can fully relate about the "managing the TW" statement.
We have only recently entered the whole TW scenario and it's kickin our buttocks.....

Seems like everytime I turn around there's some other "issue" with the whole working in a multi-user environment.