I have a room with several configurations and a family table. When I open the family table, the message "OPEN RECORDSET FAILED" appears. I have to click a few times to make it disappear.
How can we stop having this message every time a family table is opened?
Hello
You can start by trying to save under the part or assembly and then replace the original if it works.
In fact it is due to the use of the wizard for drilling with parts families. There is a known incompatibility (with the 2012 version only?), the bug has been reported to SolidWorks under the number SPR534076.
So no solution! Except maybe an update to SolidWorks...
Source (be logged in to your SolidWorks account for the first link):
Technical Comments: | In some cases changing the local region allows the Excel file to be opened without problem. It is possible that the source ofthis issue is in some way connected to date formatting within the Excel document One of the causes of this error is a generic issue in Foreign language versions of SolidWorks. The error occurs when special characters, such as the diameter symbol, are inserted into the design table. This may happen when a hole wizard parameter value contains a diameter symbol. Try using English version of SolidWorks to see if the issue is still reproducible. | ||
https://customerportal.solidworks.com/eservice_enu/start.swe?SWECmd=InvokeMethod&SWEMethod=GotoRecord&SWEService=SWGotoRecord&ViewName=SW+All+Defects+List+customerportal+-+Search&BusObject=Product+Defect&BusComp=Product+Defect&Id=1-OG8LWD&SRN=
https://forum.solidworks.com/thread/55554
Hello
Do you have laminated holes on your workpiece? If so, you must come across the same difficulty as this gentleman: https://forum.solidworks.com/thread/55554.
The defect was apparently reported to SolidWorks by the SPR534076.
Which version of SW do you use?
So maybe two solutions (in addition to the update):
- we remove the diameter Ø symbols in the part family
- we use SolidWorks in English...
Clarification: I use Solidworks 2013 and 2014. (error message on both versions)
So in fact the bug has not been fixed since the 2012 version, there are no other solutions to test than the one I proposed before: