Insufficient memory to execute the operation

Macro
1

Hello

I have a problem that is as annoying as it is weird. As you must, now the knowledge due to all my posts, I made a design with a family of parts. Until yesterday I was always able to open my family without problems and modify what I wanted in it, but for a few days now, I have been coding a macro. Since then, I can't open it and I have these messages:

So I did several tests:
- Opening an Excel file, it works,
- Opening my room and the family from another location, it doesn't work,
- Open from two other computers, so it doesn't work my computer or my software,
- Changing the configurations works (weird),
- Open with SW 2017 Premium (I have 2015 basic), it doesn't work,
- Save the family as an excel file directly from SW, it doesn't work
- Save the part under another name and insert a new Excel file (because precisely for this kind of problem I make a separate excel backup by copy/paste) it works!!

I'm a bit lost and annoyed because I have two other files in the same case but I don't have such a recent backup of the family...

That's why I'm asking you if you've ever had this problem to prevent it from happening again and maybe get back the families of my other families.

Thank you and have a good day

2

Hello

I am with SW 2016, is it possible to give us the part?

may the force be with you.

 

1 Like
3

It's nice of you, but I can't pass on my company's documents.

4

Doesn't your macro have a loop that would have overloaded your Excel file? 

1 Like
5

I think that must be a problem

_de cat that kills its tail _

you may be asking a little too much ;-)

Your families of parts and jams must surely be in a long way

so maybe lower your hopes of automating what can't be

@+ ;-)

 

1 Like
6

MaD, gt22 I thought about this cause but why now that I have recorded otherwise it works with the same workbook and the same macro? 

And if that were it, I could still open my excel file without going through the macro, right?

If ever, is it possible to know "which loop overloads the file" please?

7

In my opinion the only place where you will find the solution to your problem

if there are these here

https://www.developpez.net/forums/f664/logiciels/microsoft-office/excel/macros-vba-excel/

me and macro don't do it at all

Already you say solidworks 2015 / solidworks 2017

so 2 different versions you have to convert your 2015 files to 2017

I think that the protocols of 2015 are not the same for SW

After that, are the  excels the same?

You say impossible to read via Excel 2010

Is your operating system the same on every PC

Soliworks 2016 and 2017 does not work with Windaube 8.0 64 bit

but with windaube 8.1 64 bit it works

See here

http://www.solidworks.fr/sw/support/SystemRequirements.html

http://www.lynkoa.com/forum/solidworks/solidworks-resource-monitor-alerte-%C3%A0-13-de-la-ram#answer-732454

http://www.lynkoa.com/forum/import-export-formats-neutres/message-m%C3%A9moire-syst%C3%A8me-insuffisante-solidworks#answer-700100

hoping to have given you a good lead

@+ ;-)

 

8

Classic bug known with Office and SW (version or evolution of office (xls, xlsx, display formatting), related or not to SW).

Not related to macro, I never use it for my excels.

 

Method 1:

To try to solve the problem: try to open the PRT, then directly right-click in the excel in the tree and "save as" put it on the desktop, then try to open the file by Excel.

If he succeeds, he will probably propose a "Repair", otherwise try to do it manually by Excel.

 

Method 2:

with EPDM, recover an earlier version of the file, and save the excel on the desktop, repair it with Excel, both for the config add that has been lost, you will have to redo them.

 

Method 3:

Make a backup copy of the QQPART file, open the original file and delete the Excel from the file, save the file and close it in SW, then re-open it, and try to do an automatic re-creation of the Excel.

This method complements method 1 or 2. allows you to rebuild an almost complete excel, by recreating an excel from method 1 or 2 and method 3 for the latest added configs.

 

And otherwise, from now on for any work with an Excel included in a SW file, on the condition that you work on it by right-clicking "open in a new window" under SW,

You have to make copies of backups before leaving the file, and create a folder to put all the Excel backups ,

So before exiting the file, use this method:

Re-open the Excel with right click "Open new window", then in Excel do "Save copy as" and put it on the desktop (then move the Excel file to the Backup folder).

4 Likes
9

Hi all

I'm coming back to this post because I still have the problem and I think it's a loop that overloads my Excel file as indicated by MaD because when I open my part the family of parts is accessible but when the macro is launched I can't anymore. And the macro can't run in its entirety either because it "no longer has access" to the excel file.

I think it's the loop to fill an over-charging ComboBox. I have a list of articles in an Excel file and I want to fill them in a drop-down menu for the user to choose.

EDIT: Big discovery the macro has nothing to do with it (olivier42 Sorry to have countered you)! Because it works with some of my files and even without the macro I have this problem. I don't know what it's due to or how it happened or how it works but:
The problem comes from opening the coin family, normally I always open the family by doing "Edit in a new window" but in the macro it opens directly in SW. Yes, so what...? You will tell me well the problem comes from there because when I open the family directly in SW, the table is displayed but only partially and I can't navigate in it. As an attachment you will find what I have on the screen when I edit my part family.

From there to say that I know why this generates a memory problem, I don't know.

EDIT BIS: I'm re-editing this post and I think it's the last time but I've solved my problem! In no way can I explain the problem or how I was able to solve it, I really think that it is a SW bug and that I went to the limits. As seen before I had a problem with the family so I imported a new excel file, removing the "freeze cells" display, I zoomed out to lros the recording to have the whole table and it works!

Many thanks to everyone for your help!


capture.png
11

So it was the same problem, even if the behavior was a little more hazardous:

Bug in Excel-SW (file version, xls, xlsx, display setting, formatting, etc...)

 

So much the better if in the end you got out of it.

(always remember to make excel backups, just in case...)