John, Perry,Craig,

Now its morning in Hong Kong we have done some tests with the following results:

Note the target machine has dual boot into server and workstation on different drives. Both gave the error mentioned before.

1. Created setup for the one line program that puts a message on the screen using wait window and installed it on the target system server. We get the same result!

2. Installed foxpro development on the same machine ... it now works!


3. De-installed foxpro development ... still works.

4. ..... and finally re-booted to the target system workstation and copied over the "run times" from the other environments windows\system ... it still works!

So I guess we have concluded from 1 and 2 that it was some configuration problem but even the setup does not fix it. I guess we conclude from 3 and 4 that its something to do with the dual boot configuration and maybe Foxpro is searching the wrong directories for what it needs (just a guess).

Since this is not a normal production configuration for us and we have overcome the problem we will not spend any more time on it.

However, I think we have learnt that if our application ever uses ODBC we will need to install it properly ... and from what you say there may be other conditions we need to be wary of.

Many thanks for your assistance.

Richard