The only location syntax that seems to work "as advertised" is a directory pointer. This is fine in development mode but not to deploy. Am I missing something? Here's what I've tried.

* volume=CONVDATA" ;*Doesn't work

* volume=OI_CONVDATA" ;*Doesn't work

* volume=C:\REVSOFT\MASTER\CONVDATA" ;*This works

 Create_Table( volume, "MERGE_TEMP", "1", "MASTER", "", "")

 Create_Table( volume, "MERGE_TEMP", "", "MASTER", attriblist, "")

* volume=CONVDATA" ;*Doesn't work

* volume=OI_CONVDATA" ;*Doesn't work

* volume=C:\REVSOFT\MASTER\CONVDATA" ;*This works

I think OI doesn't work with paths one level below REVSOFT\OINSIGHT if you leave the rest "naked". However, you can leave the Drive Letter out and use a relative path. For example, we use \REVSOFT\OINSIGHT\RTDEPLOY\CONVERTS and it works just fine. Note the fact that the drive letter is missing. This would be dependent on drive mapping in a Network.

Don M.

Thanks, Don. That worked fine.

I've avoided this command because we'd have to deploy with development ready license.

Unfortunately this app inherits a lot of old (ie: bad) AREV code that's just too much rewrite. We should have built one table with multiple part key and then we wouldn't be here.

Thanks again.

Allen

Don/Allen,

In cases where an absolute path works but not a relative one, I calculate the absolute path from the relative with

Abs_Path=Drive() : "\" : Rel_Path

(Did I miss the point?)

- Oystein -

Oystein ..

Why not. Works. Mostly, a relative path seems to work if you start from a folder off a "root" directory.

Don M.

Oystein,

Good suggestion. I have used the Drive():directory method to calculate paths too. You might look for a colon in the path to determine if the drive needs to be appended. But I also need the path "..\PATCHES" to work in OI. After all, who says the customer will install the software in the REVSOFT folder?

This problem also comes up for me where in an entry field, the user enters the path "..\PATCHES" and the system attaches the volume "E:\REVSOFT\PATCHES". The data in the entry field is unaware that the path is switched by OI, which causes lots of grief in trying to reference the entered path.

Can anyone explain why OI shouldn't use standard path designations in volume attach?

Gerald

You could use the trick to open a known table that is guaranteed to be there (I use the .EXE). Then, by examining and parsing the file handle, you could get what you need including the drive letter and where filelives.

Don M.

View this thread on the forum...