V1.1a loadmap fix seems to have affected import data instead

[TimWest]

Every time that I now import data using a script I get an error message saying "could not find map file ...." !

This is because you are using the keyword IMPORT for both importing data and for importing maps!

[Tim Vasquez]

Holy cow, you are right. I have changed the data load command to INGEST and left the IMPORT command for loading maps. No doubt this is the cause of the strange behavior you noticed in your previous messages, as IMPORT would cause both actionsto occur.

I will put out a V1.1b today that will fix this.

Tim

[TimWest]

Thanks Tim!

[Roy Leep]

I am still getting the error:

Could not find map file c:\digatm\data*.*"


this is with the b version.

Roy

[Fred]

Message still exists in v1.1.b.

Fred

[Tim Vasquez]

But what is the command being used?

[Roy Leep]

Tim:
The command after downloads are completed is:

importing workchart (c:\digatm\data\*.*

information box appears twice and when these are cleared, script continues to completion.

[Fred]

In my case (V1.1.b) the message is still the same as the previous version: Could not find map file d:\Mijn documenten\Digital Atmosphere\data*.*"

Fred

[Roy Leep]

I also note that even though the script continues after the information window. That all data is old it appears to be data from prior to my installing version 1.1b.

Roy

[Hendricusl]

Tim,

it appears to be the "import" command. Scripts that were working fine with this command now are receiving the error messages. Here is the command I am running:
import,F:\DigitalAtmosphereWS\data\*.*

Here is the resulting error message:
Could not find map file F:\DigitalAtmosphereWS\data\*.*

In the previous version I was using this command just imported data.

Hendricus