solidworks >> ISSUE ON SW2006 S.P.0-Database and Hole wizard error

by ziaciacia » Tue, 21 Feb 2006 07:43:56 GMT

We tried to install on four PCs (Dell Dimension- XPpro-SP2) SW2006.
Everything went smooth during install process.
But when we tried to use the hole wizard SW gives an error message
like:"unable to open the database.." ,the command stops so that no hole
could be introduced in the part.
When we exit from command SW works fine and does not crash..
Also if I try to modify an existing part with hole in it, I can edit
function, but immediately the error message appears and stops the command
(however SW does not crash as well).
I've read already some threads about this issue and I tried all the
suggested solutions, but none worked.
Our reseller suggest to format the PCs, but if possible I wouldn't do it
(several other software to install again-lot of waste time).
Any suggestion, gentlemen?

Giorgio from Italy



solidworks >> ISSUE ON SW2006 S.P.0-Database and Hole wizard error

by Boone1963 » Tue, 21 Feb 2006 22:19:04 GMT


I had some problems with 2006 sp0.0 hole wizard. My VAR suggesed the
following:

Close SolidWorks then browse to C:\Program Files\<SolidWorks install
dir>\data\ and rename default.mdb to olddefault.mdb.

Then restart SolidWorks.

This fixed my problem, worth trying.

Boone

solidworks >> ISSUE ON SW2006 S.P.0-Database and Hole wizard error

by SWX-VAR-JP » Wed, 22 Feb 2006 02:59:17 GMT

This can be an error with file registration. Before you throw in the
towel, try registering these files again and restart the computer.
Then see if that doesn't fix the problem.

1. C:\Program Files\Common Files\System\ADO\msado15.DLL
2. C:\Program Files\Common Files\System\Ole DB\oledb32.DLL
3. C:\Program Files\Common Files\system\ADO\msadrh15.dll
4. C:\Program Files\Common Files\System\ADO\msadox.dll
5. 5. C:\WINDOWS\system32\MSJTES40.dll (use if no database access is
possible)


To register a dll:

1. Close SolidWorks if it is currently running and Open a command line
window (DOS window).
2. Change Directory (cd ...) to the location were the .dll file of
interest resides.
3. At the command prompt, type: regsvr32 "name of .dll file"
(without the quotes).
4. Once you press Enter to run the command you should see a dialogue
pop up saying the action was successful.
*to unregister a .dll file just use the command: regsvr32 -u "name
of .dll file"(without the quotes).

Similar Threads

1. help in trying to add an entry to a Hole Wizard database

2. Hole Wizard error

 SWX 2004 SP1.0, Win2K, Hole Wizard error
"Error: The database file '[snip long folder descrip]\swbrowser.mdb' is not
the expected version (8.7)"

 I tried calling up tech support, but I guess they have the day off.
Lucky guys. ;-)

 Any ideas here?
My Rod really needs a threaded hole in it.

Thanks


3. Hole Wizard "out of memory" error

4. Hole Wizard Holes Changing by themselves~?

I have an engineer here who says that he puts a hole wizard tap hole in
a part and later, he finds that the hole becomes a different size.

Does anyone else see this happening?

We are using 2006 SP3.1, and our toolbox and hole wizard are on a
network drive. We have 25 CAD systems pointing at this network drive
location.

Thanks,

Mark

5. disable certain hole wizard tapped hole sizes?

6. Reamed holes in the hole wizard?

Hi all,

I often need to put reamed holes in the parts I am designing for dowel 
pins etc. Is there anything in the hole wizard that allows this? 

Often, I need say for a 6.0mm dowel, a 6.020 oversize reamed hole, and 
was wondering if there is a way to do this with the hole wizard, rather 
than manually doing it (so the info turns up in the drawing)?

TIA,

Joe


-- 
Remove nospam when replying

7. Plotting to a RIP VIA .ps or .pdf (Paper size issue)

8. Base Part location issues - SW2006

I'm encountering a problem when inserting a base part into a new part. 
Similar to inserting the first part into an assembly, you drag the part 
to the origin. The symbol appears to indicate that the part will lock 
onto the origin and you release the part.

The problem is that the appropriate plane of the base part isn't the 
same as the corresponding plane of the new part, hence the part isn't 
centralised and it is often close enough to not be noticed until it's 
too late.

I'm still using SW2006 SP3.0

Has anybody encountered this and was it resolved with a later service pack.

Any suggestions.

John