Strategy For Moving App To Server for Multi User 1

[drosenkranz]

Hello,

In finishing my multi-user application (yeah semi-newbie), I'm going to place a copy of my project data on the server. This will include the files:

MyApp.pjx, .pjt, and All of my tables with the .dbc, .dct, and .dcx.

My EXE will include the forms, programs and reports.

Here's the newbie questions part... tell me if this is correct?

1) Do Local views reside in the poject on my local hard disk? They are referring to FoxPro Tables in the database container that I'm putting on the server.

2) When I compile, they too (local views) get included in my EXE?

3) What's the difference between Set Path and Set Default with respect to my Local Views accessing the tables that will now be residing on the server?

4) Any strategy on Client Server migration appreciated?
The 2nd mouse gets the cheese.

 

[rgbean]

1) + 2) Local view (definitions) are stored in the .DBC not in the .EXE.

3) SET DEFAULT specifies the current directory, where to first look for any non-path qualified files and where any newly created files will exist. It can only be a single path entry.
SET PATH is where and files that can't be found in the SET DEFAULT path are looked for - it can include multiple paths and can be modified indirectly by the use of things like GETFILE().

All tables (and indirectly local views) normally use relative pathing based on the location of the .DBC. So if the tables on the server are in the same relative location (pathing) to the .DBC on the server as they were in development, you shouldn't have any problems.

4) There a whole section in the help file on this topic. Perhaps if you have some specific questions.

Rick

 

[drosenkranz]

Thanks for the help Rick. I have read the chapter (and others) but I'm being tripped up by VB programming experience and mfoxplus memories from the late 1980's. LOL. My current employer wants VFP (but doesn't want to pay for any training) so I'm re-learning on the fly from books (and Tek-Tips).

I thought the local views were physical objects but I'm realizing they are nothing more than SQL Select Statements that are stored within the database container. All of the apps I've done since returning to VFP have been single user apps with tables. This is the first multi-user VFP project (using local views). Just couldn't see the basics of what I was dealing with- but local views function like the Select statements used in creating recorsets in VB.

Thanks for the response (and your patience with the VB impaired)
The 2nd mouse gets the cheese.