Using 3.2 is causing a strange error.

[Nicholas Moran]

I don't have a way to change anything in the file I am entering data into.

using 3.1 works but destroys the active x buttons. Using 3.2 seems to work but cuases the error below. 

I am not sure what to do about it. Any help?

<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<logFileName>error395280_01.xml</logFileName>
<summary>Errors were detected in file 'C:\Users\nick\Scripts\rfctospi\newgeneratedspi.xlsm'</summary>
<removedRecords>
<removedRecord>Removed Records: Named range from /xl/workbook.xml part (Workbook)</removedRecord>
</removedRecords>
<repairedRecords>
<repairedRecord>Repaired Records: Drawing from /xl/drawings/drawing5.xml part (Drawing shape)</repairedRecord>
</repairedRecords>
</recoveryLog>

[Charlie Clark]

On 7 Aug 2024, at 16:48, Nicholas Moran wrote:

> I don't have a way to change anything in the file I am entering data into.
> using 3.1 works but destroys the active x buttons. Using 3.2 seems to work
> but cuases the error below.
> I am not sure what to do about it. Any help?

The error message just tells you that there's something in one of the drawing files that Excel doesn't like.

3.2 isn't supported so you should really only use it if you're prepared to get your hands dirty with sorting out any problems.

Charlie

--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Sengelsweg 34
Düsseldorf
D- 40489
Tel: +49-203-3925-0390
Mobile: +49-178-782-6226

[Nicholas's Gmail]

Understood, the problem is 3.1 messes up activex buttons and I need that to be preserved. 

The error mentions a drawing but also mentions a workbook. I can’t tell the difference between the old file and the newly generated file so I don’t know how to track down the error. 

I also can’t tell if it’s something I can safely ignore, though this app I’m making is for non technical users so I don’t want a scary warning showing up if I can help it. 

Do you have any hints as to how I can start my troubleshooting?

Unfortunately this xlsm file is password protected so I can’t unlock certain fields and I can’t unhide things either. 

I didn’t think that would be a problem because I have used vba for the same process and also 3.1. Neither produced this error. 

Nicholas A. Moran, PG

Environmental Consultant | Geologist

https://moran.rocks/

On Aug 7, 2024, at 11:07 AM, Charlie Clark <charli...@clark-consulting.eu> wrote:

--
You received this message because you are subscribed to the Google Groups "openpyxl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpyxl-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/openpyxl-users/3B6FD377-590E-4C82-A490-74104ACDF026%40clark-consulting.eu.

[Charlie Clark]

On 7 Aug 2024, at 17:14, Nicholas's Gmail wrote:

> Do you have any hints as to how I can start my troubleshooting?

Yes, start with the documentation for developers and get used to working with the source XML.