loading 2005

I tried loading 2005 SW and got the error message "The database file
C:\Program Files\Common File\Solidworks
Data\lang\english\swbrowser.mdb" is not the expected version (9.02).
This comes up when I try to used hole wizard.
I did have other versions, i.e. SW 2006,04,02 on my computer at times.
These are not on the computer anymore.
How can I solve this problem? Help is appreciated.
Reply to
billyb
Loading thread data ...
Try add/remove programs and modify. Make sure you have toolbox added in under the customize section. if it is already added then try a repair or remove toolbox and then add it back. Hopefully this will repair the incorrect toolbox file.
billyb wrote:
Reply to
Mr. Who
You can 'hack' the SWBrowser.mdb file if you want.
Open it in Access and go to the table called Version. There is a field called CurrentVersion. Change the value to whatever value the error message says. Re-save the MDB file and you're done.
You may need to restart SW though.
Regards
Martin
Reply to
wurz
Manually editing SolidWorks data files seems like a really bad idea. Was this fix endorsed by SW?
wurz wrote:
Reply to
Mr. Who
Mr. Who Where is the "customize section"? Sorry maybe stupid question.
Mr. Who wrote:
Reply to
billyb
THANK YOU!!!!!!!!! IT WORKED, I WENT IN WITH ACCESS AND CHANGED IT TO 9.02 (IT WAS 10.3 OR SOMETHING). ANYWAY, I DID AS YOU SUGGESTED. I REOPENED SW, AND THE HOLE WIZARD WORKED. THANK YOU SO MUCH, VERY MUCH APPRECIATED!!!!!
wurz wrote:
Reply to
billyb
Oh yeah, you only get customize button when doing a new install.
Control Panel -> Add/Remove Programs -> SolidWorks -> Modify button -> Choose your SW type (pro, premium etc) and Next -> Uncheck toolbox as a SW add-in.
Then repeat and recheck toolbox as an add-in. This should reinstall the files and hopefully fix things up.
I see that the previously mentioned fix did work, but I would have serious reservations about altering that access db value without knowing the ramifications.
billyb wrote:
Reply to
Mr. Who
Nope - not endorsed by SW, but the file is a plain old Access database anyway. I've only ever had to do this once (when a SP didn't 'take' properly) and it didn't cause any waves ;-)
Martin
Reply to
wurz
NO!!!! NO!!!!! NO!!!!! NO!!!! Don't hack your file!!!!!!!
Fix it the right way if you would have called your VAR you would have been directed to the correct way to fix it.
You have to use the UpdateBrowserData.exe
The reason the version is important is because the tables may change between releases. If you don't get the propper update you can cause a whole heap of problems in the future. The reason it didn't update is either you didn't point the install to the correct location or your swBrowser.mdbold file couldn't be overwritten.
e-mail me and I will send you a walk through document for this.
Corey
billyb wrote:
Reply to
CS
Actually now that I read your post again I see the expected version is earilier than the current version indicating it may have been updated by an installation of sw2006. Do you have that installed. If so you will have problems again when you try to use it in 2006.
CS wrote:
Reply to
CS
Mr. Wurz, You were such a big help getting my "hole wizard" working, (I went into access and changed the version number). I am not getting the toolbox to come up, it says its a "future version". The tree shows up and ends up with Bolt_AI.SLDPRT, but like I said, its says "future version". I did have SW 2006 on and took it off because I could not get it to work. Some things were set to future, now I am having trouble using the SW 2005 toolbox. Can you recommend a remedy like you did with the hole wizard?
wurz wrote:
Reply to
billyb
Your VAR should be able to help you through the steps necassary to help you get 2006 up and running.
John Layne
formatting link

Reply to
John Layne
Right now I just want to get my toolbox working in SW 2005
John Layne wrote:
Reply to
billyb
I tried this Add/Remove approach with my toolbox problem. Did not work. The problem I feel is that I have a "future" version of SW 2006 in the program for toolbox, it tells me as much when I try to use it.. How I get back to the SW2005 version is the problem.
Mr. Who wrote:
Reply to
billyb
I think really you need to be a reinstall of 05 - clean out the SW reg entries and any other lingering SW files.You will find details on the SW site how to do this properly.
Reply to
neil
It looks as if you are re-install territory - if you installed then un-installed 2006, you will most likely have a 2006 toolbox trying to work with 2005.
The only way around that is to re-install the 2005 toolbox after uninstalling the 2006 toolbox. If you are using a local toolbox directory, make sure that you remove Solidworks and the common data directiry aswell.
As was stated before in this thread, your VAR should sort this for you in a snip.
Reply to
wurz
IT WORKED, THANKS FOR THE SUGGESTION, MY TOOLBOX IS WORKING I GOT RID OF THE COMMOND DATA FOLDER IN ADDITON TO THE UNINSTALL AND THEN RELOADED OR RE> It looks as if you are re-install territory - if you installed then
Reply to
billyb
Billyb,
I can't stress enought that when you have problems like this you have to contact your VAR. The actions you just took will cause other problems. Try this find an assembly that you created using parts out of the toolbox........OK do you see the huge fasteners. They are huge because the actions you just took removed all the configuration data you had created through the use of toolbox in the past. There is no way to recover this data without re-inserting each fastener again. The reason you were having problems in the first place is because after you upgraded to 2006 you had updated each part file in the toolbox folders to 2006 and since no parametric modeler has backward compatability you can no longer open those files in 2005 the only way to recover your data in 2005 is to replace the files with the back-up you should have created before upgrading. I just hope you aren't sitting on alot of assemblies that used toolbox parts.
Sorry, Corey
billyb wrote:
Reply to
CS

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.