I have a client that keeps data on a sharepoint file site and maps that location to a network drive on their computer. He tried to load a shapefile from that drive to our product which did not have an .idx file and by default we have coded our software to create the index file. Once the code tried to create the index, we got the following I/O exception error.
In the past, I have found that we can’t load or export data to drives referenced with UNC paths, but in this case he’s mapped the drive. Since the BuildIndexFile() function is part of Mapsuite, we can’t see what path type its using to know if maybe it’s converting it back to UNC to draw the error.
Client can copy files to/from the shared drive through normal windows explorer, so there should be no issue resolving the path.
Also, in my testing with mapped network drives, I can not replicate the issue so potentially it is specific to sharepoint.
This shared resource is very important for the client to keep their data and we need to be able to reference GIS data directly from this drive instead of making local copies on multiple users machines. Any ideas?
We are using version 9 Mapsuite.