Forums
|
Forums >> General Discussion >> Revit Project Management >> local file saving location
|
|
|
active
Joined: Sun, Jun 24, 2007
592 Posts
 |
twice daily
-----------------------------------
I like scooters. and motorcycles. |
This user is offline |
|
 | |
|
|
active
Joined: Mon, Mar 20, 2006
219 Posts
|
"...our office standard for opening a Revit file at ANY time is to make a new (and single) local EVERY time."
|
This user is offline |
|
|
|
active
Joined: Fri, Sep 29, 2006
10 Posts
No Rating |
oghh so you guys are opening the file everymorning from central? isnt it a bit dangerous?
|
This user is offline |
|
|
|
active
Joined: Mon, Mar 20, 2006
219 Posts
|
No no...every morning I go to the network folder and copy-paste the central file into my local folder (overwrite? yes) and then double-click the newly made local file to open. Just answer Yes to the Revit dialogue that makes sure you realize what you are doing. Same after lunch or switching back to the file after closing it out....ANY time I'm opening a project file. If nobody else has been in it, then it's a little bit overkill, but the very little bit of extra time is worth developing the good habit and having a clean, unconditional office standard.
|
This user is offline |
|
|
|
active
Joined: Thu, Dec 16, 2004
792 Posts
 |
Wait... so you actually copy/pate the central file into your local machine to create the local copy? Interesting way to get the local file. " It is generally recommended that you create a local copy of the central file every day. - Open the central file.
- Click File menu>Save As.
- In the Save As dialog, navigate to a location on your local network or your hard drive.
- Enter a name for the file, and click Save.
" - Revit Help I typically just use the local file that is on my machine every morning when i get into the office. When i open the local file on my machine, it automatically updates the latest revisions from the central file. If for some reason it does not, I just Reload Latest (RL). I have not found a need to make a new local file every day even though it is recommended. I've found that if something happens with connectivity to the central file it was ALWAYS something bigger than not making a new local file (ie: someone "hacking" at the central file or renaming the central file, in which case you would need to make a new local file no matter what). I have not had to recreate this local file since I started work on this project 3 weeks ago. There are 4 other people working in the model along with me.
-----------------------------------
-//------------------------
Carl - rkitecsure[at]gmail.com
Need help? I'm probably in my chat room!
You fell victim to one of the classic blunders. The most famous is never get involved in a land war in asia, but only slightly less well known is this! Never go in against a Sicilian when death is on the line! |
This user is offline |
View Website
|
|
|
active
Joined: Mon, Mar 20, 2006
219 Posts
|
We use the copy-paste method described in our office for a variety of reasons: 1) Copy-paste is faster than a Save to Central 2) Less chance someone accidentally stays in the central without making a local 3) decreases chance of corruption. 4) Solved a circular Element Borrowing issue and verified better control of EB in general. 5) Small but tangible performance increases. 6) Small but tangible file size reduction.
|
This user is offline |
|
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
WOW!!! We all use only our local files and just RL in the morning and we never have any problems. Opening a new local every day would really tax our network. We do have our project managers audit the central at least once a week .... especially after the project hits 80 meg. That verifies the file and compresses it. .... don't know what's up with your systems but ... Since 2008 was installed, nobody can work in the central file. When you open the central, we always get a message that the file is being considered as a local file being used by "..." and if you want it to remain as a central, you must save it as such when finished.....
|
This user is online |
|
|
|
active
Joined: Thu, Dec 16, 2004
792 Posts
|
One other point i would like to bring up about making a new local file every morning. This particular project I am working on is an 87 mb central file, medium in size when it comes to revit models. Once a week our project managers work from home via VPN. Normally we're required to have the local file of a workshare project on our machines before we go home in the evening before our work from home day, but this particular time, the central file was not ready to be copied from. So the next morning I got to spend 2.5 hours opening the central file over VPN (and I have a 10mb connection at home) in order to make my local file. Now that I have the local file on my machine, I can work from home and be connected into the central file in less than a minute. If I made a new localfile every morning, that would be a wasted 2.5 hours because of the VPN encryption/decryption.
-----------------------------------
-//------------------------
Carl - rkitecsure[at]gmail.com
Need help? I'm probably in my chat room!
You fell victim to one of the classic blunders. The most famous is never get involved in a land war in asia, but only slightly less well known is this! Never go in against a Sicilian when death is on the line! |
This user is offline |
View Website
|
|
|
active
Joined: Sun, Jun 24, 2007
592 Posts
|
Okay, so file size reduction is better when you make new locals. obviously you don't have to make new locals but its always been a best practice thing as far as I can remember. If your using vpn then obviously making new locals would suck because its so slow. Lets beat it some more though. How often do you guys purge all unused?
-----------------------------------
I like scooters. and motorcycles. |
This user is offline |
|
|
|
active
Joined: Mon, Mar 20, 2006
219 Posts
|
Purge Unused? Just each time I change from working in one view to another. Why? Doesn't everybody?
|
This user is offline |
|
| |
|
|
site moderator|||
Joined: Tue, May 16, 2006
13079 Posts
|
First - I could care less about the users local file size. I care about the network file size and auditing that once a week handles that problem. We only purge unused when we are ready to archive. We start with a compact template - add as needed and the project manager deletes unused families individually when they are no longer needed. Purge unused can get you in trouble.
|
This user is online |
|
|
|
active
Joined: Thu, Dec 16, 2004
792 Posts
|
" We use the copy-paste method described in our office for a variety of reasons: 1) Copy-paste is faster than a Save to Central 2) Less chance someone accidentally stays in the central without making a local 3) decreases chance of corruption. 4) Solved a circular Element Borrowing issue and verified better control of EB in general. 5) Small but tangible performance increases. 6) Small but tangible file size reduction. " I am only rebuttling this from my experience and understanding of the Revit workshare system so that there isn't a thought planted that this is how the tool was meant to be used. Based on what you are stating, I'd be interested to see exactly how your office is running workshare projects. 1) You shouldn't be copy/pasting when saving to central. You should only be doing that when creating a local copy. The reason copy/paste is faster (if you are using it to save to central) is because Save to Central does more than just copy the file location. StC updates the database in the central file, checks for changes in the central file that are not present in your local copy, updates your local database if changes are present and finally updates elements borowed. Copy/paste just transfers the ones and zeros. If you are referring to the Save As method from the central file to create a local file, I would highly doubt it's faster as you have to wait for the time it takes to copy/paste, then the time it takes to open the new file and then the time it takes after you hit ok on the "Are you sure" dialogue for the connections to be made between the local and central file. When you open the central file and use save as, all you have to do is wait for the file to save to the local location before you can begin working. 2) This I can see, but that's like saying someone lost work because they didn't save before closing. Creating a local file should be second nature in a workshare environment. The only con to having someone work in the central file instead of a local file is that that person has complete control over worksets. I've actually used this method to manage workshare projects so that the production team could not make accidental changes without my permission. 3) I'd like to see the stats on this. Corruption never occurs on projects that I use the recommended method with. Corruption tends to occur when a save to central is interupted (which would also happen if a copy/paste were interupted), when someone "hacks" the central file and only on rare occasions does it happen for reasons that I have not been able to identify. 4, 5 and 6) From these claims I'm not sure if there's a miscommunication as to what you are referring to as a local versus central file or if your office is not using this tool as it was meant to be used, but if it's working for you, then I can't argue with it. The local file is the same type of file whether you copy/paste it or use the Save As method to create the local file from the central file. There file size varies from local copy to local copy as each local file contains different types of information (different worksets are open and editable in different local files, therefore the database is going to contain different information from file to file.) WWHub, if you are getting that message when opening the central file, then you are not opening the tru central file. If you open that file and then go to file > save to central it will give you the path of the central file it is tryin gto save to. If that file is not present, then your central file has been moved.
Edited on: Wed, Jul 9, 2008 at 11:15:40 AM
-----------------------------------
-//------------------------
Carl - rkitecsure[at]gmail.com
Need help? I'm probably in my chat room!
You fell victim to one of the classic blunders. The most famous is never get involved in a land war in asia, but only slightly less well known is this! Never go in against a Sicilian when death is on the line! |
This user is offline |
View Website
|
|
|
site moderator|||
Joined: Fri, Feb 10, 2006
1874 Posts
|
Here's some info on Purge Unused from the RevitOpEd blog: Today an adventurous Revit user thought he'd use Purge Unused unsolicted. This during a day long excursion into the workset environment with fourteen concurrent users. We discovered this when I gave the gang the task of sketching some interior partitions on "their" floors and we were a bit surprised to find only three walls in the project. So I casually commented that could only happend if someone chose to delete them or use Purge Unused. At this point one of our gang volunteered, "oh I did that!". Much laughter and conversation ensued between the rest of us.To fix the problem of missing stuff, we used Transfer Project Standards. That's when bumped into the next issue or gotcha.If you create new elements in your local file while someone else uses Purge Unused in their local and they STC (Save to Central) first, guess what happens to your stuff. It goes away! That's what!Logical and consistent with the existing relationship of local files and central file. However it seems to me that Purge Unused ought to be a bit "smarter" or disabled except under special circumstances like working in a central with no other users or no other uses while in a local perhaps.It was a first for me, nobody has used Purge Unused before without first asking about the feature. Remaining "half full" it's better that it happened during a training session than on a live project! HTH
-----------------------------------
best regards, coreed,aia bmpArchitects,Inc. "Revit has to be implemented, Not installed." Long Live Revit |
This user is offline |
|
|
|
active
Joined: Fri, Jan 11, 2008
42 Posts
No Rating |
rkitect, you can take a copy of the central file when you leave the office in a usb jumpdrive, replace you local file at home, and just reload latest when you open it over the VPN to load the latest changes... instead of copying the whole central file over the VPN. We also create copies of the central file after major deadlines. So we have the SD/DD/CD and progress set copies of the central file just like it was the day of the issue, for our records. With that we can recreate those sets as they were....
|
This user is offline |
|
|
|
active
Joined: Fri, Jan 11, 2008
42 Posts
No Rating |
We never "purge unused", you might loose office template stuff that you might need later on in the design process.
|
This user is offline |
|
|
|
Similar Threads |
|
Location of Central File and Local File |
Revit Systems >> Technical Support
|
Tue, Nov 15, 2011 at 3:46:53 PM
|
2
|
|
Revit local files = Workstation or server location |
General Discussion >> Revit Project Management
|
Mon, Mar 11, 2013 at 7:31:30 AM
|
1
|
|
Can not create local file from Central |
Revit Building >> Technical Support
|
Tue, Mar 6, 2012 at 11:57:26 AM
|
7
|
|
Error - Local File Resides in Central File Location |
Revit Systems >> Technical Support
|
Fri, Apr 9, 2010 at 8:34:55 AM
|
2
|
|
Central File Path on a local file |
General Discussion >> Revit Project Management
|
Sat, Oct 24, 2015 at 10:21:20 AM
|
1
|
|
|
Site Stats
Members: | 1988829 | Objects: | 22877 | Forum Posts: | 152178 | Job Listings: | 3 |
|
Search