Binding to table in current directory

[fjvalencian]

Hi,

How can I bind a table to an Excel in the model's current directory so that I don't need to do the binding again when running the model from other computers?

[agraunke]

Will the excel file also be on the other computer(s), or is it network accessible?

You can use relative paths for binding-- if the data file is in the same folder as the Simio model, you can just enter the file name:

 

If the data file is on a network, you should be able to update the data from the model running on any computer attached to that network with the appropriate permissions.

Also, once imported the data will remain in the table even if the source is no longer available. It won't update if the source data changes, though.

-Adam

[fjvalencian]

Thanks for the response!

It'll be used in other computers in different networks. I tried your solution but it doesn't seem to be working. If I remove the directory it stops recognizing the file.

[agraunke]

There are two approaches that should work:

1. Local data with relative file paths.

In this case, the Simio model and data file need to be in the same directory as each other, on each computer where you want to run the model. The file path in the binding dialog box would look like the image my first post. A downside is that the data may become difficult to manage if you need it to remain consistent, as it must be duplicated to each machine running the model.

2. Network data source

Here the binding info would point to a data source on a network-connected computer/server. The model file will remain bound on any computer that has network access to the linked data source. The data only exists on the network, so there are no concerns with data consistency, but any machine must be able to access the data location for any updates to get pulled into the model.

Are you trying either of these, and if so what specific error are you getting? What sprint are you using?

-Adam

[dsturrock]

In Adam's second case it is important that all users map the network drive in the same way. For example if it is mapped to drive M: by the model builder, all users must also map it to Drive M:.

[agraunke]

Alternatively, instead of using a mapped drive you can use a network location (i.e. \\servername\sharedfoldername\filename.xlsx).