Hi All

I am confused and unfortunately a search for FS109 didn't really seem to lighten that confusion, so I am after suggestions

We attach our tables upon logging into our application so that during development we can test against different clients data.

One set of tables that we were previously using regularly have just started to not attach. No changes have occurred that we can think of.

The scenario is as follows.

Directory structure

T:\clients\client1\multipledirs_with_tables

T:\clients\client2\multipledirs_with_tables

T:\clients\client3\multipledirs_with_tables

3 Different versions of application

1 Local - attaches all 3 clients above without problems

1 Network drive (P) - attaches all 3 clients above without problems

1 Network drive (T) - attaches 2 clients without problems, client3 does not attach. Investigation of error status returns FS109:@vm:path

Symptoms reproducible on multiple workstations. P and T different mappings but same server

Any more info required, please ask

Any suggestions are more than welcome.

Mark

Mark,

I have seen FS109 when an app tried to alias tables in an empty folder. (The folder was meant to contain a volume, but by a mistake the client had removed all the files.) I don't say you have an empty folder, but is there something that might make that folder somehow inaccessible???

I have seen FS109 when there was an error in the volume name parameter. (This was with Copy_Table.)

I have seen FS109 when a function tried to alias tables and the volume name parameter contained an absolute path. I never solved that problem. Are your paths absolute? I know it's not always possible, but can you try with a relative one?

I think I also would check if the path returned along with the error code is the path you expect it to be. If it's different that might be a clue.

- Oystein -

Oystein,

Thanks for the suggestions

I don't believe there is anything making the folder inaccessible.

If there was, I would expect to not be able to attach the data from any version of the application.

However I can do this from all other copies, both local and network.

As for an error in the volume name, again the volume name is the same in all other copies of the application.

The Attach_Table function is using an absolute path but any thoughts on why that would matter on the one application, and why now when it has been working successfully for at least 12 months?

The last suggestion was a clue I had tried for myself and unfortunately, the correct path is being returned.

Here is some new details that may help the more knowledgable than myself out there.

We have some new data from a different client that we have applied the same process to. The attaching of this volume is providing the same error message but only intermittantly. I mean that sometimes when we detach one volume and attach the new volume, it works as expected. Other times it produces the FS109 error. If we get the error we have to shut down the application and log back in, in order to be able to get to that data. With the volume mentioned in my original posting, we get the FS109 every time.

As always, your help is appreciated Oystein

If anyone else has any ideas, Please speak up…

Mark

View this thread on the Works forum...