Export of Excel file from the Visio file created by FlexSimTemplate.vst fails

Question

question

Sakamoto Ko asked Dec 18, '23 Sakamoto Ko commented Jan 9, '24

Export of Excel file from the Visio file created by FlexSimTemplate.vst fails

Hi.

I am investigating Visio Importer.

However, it does not work with the following error message.

Could you please check if you can export the vsdx file I created to an excel file?FlexsimTemplate.zip

Maybe I should change the field settings in the database export wizard, but I didn't know which data type to change each field to.

Thanks in advance.

Software Version:

FlexSim 23.0.11

visio

1702895860086.png (50.0 KiB)

1702895883490.png (27.3 KiB)

flexsimtemplate.zip (28.8 KiB)

· 8

Kavika F ♦ commented · Dec 18, 2023 at 05:51 PM

Hey @Sakamoto Ko, because of the error presented, have you tried the solution provided by Microsoft? They talk about how you may have too many internal fields defined and need to either compact the table or create a copy of it.

0 ·

Sakamoto Ko Kavika F ♦ commented · Dec 19, 2023 at 09:20 AM

@Kavika F

Thanks for your reply.

I had seen this article before but did not specifically try it because I thought it was a solution for Access.

I changed the export destination to a new Excel file because I didn't think Visio could do the operations described in this article.

Then the s1001 error did not occur, but the s1004 error did.

In fact, the first error I saw was s1004.

I then repeated the export with these fields in isolation to determine the cause of this error.

Perhaps this operation caused the number of internal columns to be larger than 255.

However, the cause of the s1004 error is not yet known.

I am using the contents of Visio Importer (flexsim.com) to perform the operation.

Is this error caused by the field type set in each field, since it mentions "invalid SQL data type" ?

0 ·

Kavika F ♦ Sakamoto Ko commented · Dec 19, 2023 at 05:05 PM

@Sakamoto Ko, what kind of data are you trying to write in your SQL query? That error, like you said, refers to an invalid SQL data type.

0 ·

Show more comments

Jeanette F ♦♦ commented · Jan 08 at 07:12 PM

Hi @Sakamoto Ko, was Phil BoBo's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 ·

Answer 1 · 2024-01-03T23:07:48Z

Phil BoBo answered Jan 3, '24 Sakamoto Ko commented Jan 9, '24

The Visio Importer tutorial was written with a much older version of FlexSim (version 3, from 2005) and Visio (Office10, from 2001). It may not work exactly the same with a newer version of Visio. You may need to adjust certain steps if you run into errors trying to follow the documentation.

The errors you are getting are on the Visio side, not the FlexSim side. We don't have any more information about what changed in Visio than you do. If you want it to work, then you've got to figure out what to do to make it work. If you can't figure out how to make it work, then just don't use that feature; it isn't critical.

See also: VISIO IMPORTER share model please

· 2

Phil BoBo ♦♦ commented · Jan 04 at 05:01 PM

@Sakamoto Ko

Looking at your screenshots again, the error message is pretty clear: "Too many fields defined".

I'm not sure why you added a bunch of information about the field types. The error is clearly about the amount of fields.

In the tutorial, it says to just add all the fields, but maybe newer versions of Visio have more fields by default than the export can handle, so you should only export certain fields.

The following fields are the ones that are needed:

PinX, PinY, BeginX, EndX, ShapeText, ShapeKey, Angle, Width, Height, PropRow_1 (or Prop_Row_1)

0 ·

Sakamoto Ko Phil BoBo ♦♦ commented · Jan 09 at 11:10 AM

Hello @Phil BoBo.

I will try to see if I can export based on the field information you gave me.

Thank you very much for your valuable information.

0 ·

question