From single user to multi-instances 2

[lifesupport]

I have an application that is originally built for a single user and operates as a single instance. This app is able to share data over a network as long as the app itself is installed on each individual PC. Also on each individual PC are smaller temp tables that save the user's selections and temp tables that crunch data. It has been requested that this app be altered so that it can be installed on the server as well and all users can use the same app as well as the same temp tables. This is difficult as the temp tables will pose problems. Does anyone have any idea on how this can be done? Are there any books/articles on this?

Thanks for your help.

 

[alvechurchdata]

We have a client who sounds to be running something similar. Basically it's a single-user application that's now sitting on Terminal Server so that three people can use it.

It makes heavy use of temp files and we solved the problem by setting TEMP to z:/ and by getting one of the system administrators to change the logon script so that each user mapped drive z: to their own folder on the server.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Mike Lewis]

Lifesupport,

Even though the application itself and the main (shared) tables will be on the server, you can still use the users' local hard drives for temporary tables. In fact, that's a good thing to do, partly because you will be able to create and delete files without worrying about multi-user issues, and also because it will be faster.

Use SYS(2023) to get the path to the directory where you can store these files.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[lifesupport]

This is excelent advice! Thanks

 

[alvechurchdata]

you can still use the users' local hard drives for temporary tables

Only if you do a halfway decent job of designing the app in the first place. In our case the application was littered with hard-coded references to c:\temp for things like temporary tables, xls exports and MEM files. It was an upgraded (but not rewritten) Fox 2.00 application.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Mike Lewis]

Geoff,

In our case the application was littered with hard-coded references to c:\temp for things like temporary tables, xls exports and MEM files.

I made that mistake in the first couple of applications I ever wrote. I've studiously avoided it since.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[alvechurchdata]

I made that mistake in the first couple of applications I ever wrote.

I'll have to get the source code dusted for fingerprints.


Geoff Franklin

http://www.alvechurchdata.co.uk

 

[TamarGranor]

But that kind of stuff isn't too hard to clean up using Code References.

Tamar