Setup 2 Win XP machines as Client & Server

[Guest]

Can anyone point me to a resource where I can learn how to configure two
windows xp pro (sp2) machines in a client-server configuration? I have a
shared data base application that simply refuses to run in a peer to peer
network configuration. Any advice on this situation is most appreciated.

 

[Guest]

I think before anyone could answer that, we'd need to know exactly how the
database client communicates- is it a straightforward file-share (netbios) or
does it use ODBC, or perhaps a direct TCP/IP connection?

Also, why will the server not operate? does it refuse to install on a non
server-grade OS? Or does it install but fail to work?

WinXP Pro is fundamentally the same as a 10-user 2000 Server, as far as
file-sharing is concernned. There are some specialist services that cannot be
installed onto a workstation, however, and the problem might be here.

 

[Guest]

Thanks for your reply. I asked the programmer the same questions and am
awaiting her response. Ironically, she has had to post the question in Visual
Fox Pro User's group herself. Not unlike the blind leading the blind here. As
soon as I get her response I will post here.

Thanks again!

 

[Guest]

I can, however answer your other questions. The data base client is installed
on a new PC running win xp pro (sp2). According to the programmer's
instructions, all one needs to do is share the (entire) hard drive over the
network giving read-write privileges to the other machine(s), then make a
shortcut to the application's executable file from the (networked) machine.
Specify the "start in" folder as being on the server, then its simply a
matter of clicking the icon from the remote machine to run the program.

The data base application does attempt to run from the remote machine, but
apparently has some kind of meltdown before it loads completely. When it
"crashes" it gives few, if any clues as to the reasons. It does produce a
text file apparently recording the event, but the information contained
therein is incomprehensible. I have sent the programmer this log file as well.

The network is a simple ethernet based, wired configuration connected
through a switch, and checks out fine. I can share printers over this
network, so I feel confident its working as it should.

If it helps any, this peer-to-peer network configuration is the same one an
older version of this data base program performed well on. It used TCP/IP.
The significant difference being now it has been re-written with visual fox
pro and transformed into a "windows based" application.

Not sure if this gives you the information you really need, but am awaiting
the programmer's reply regarding it's communications requirements.

Thanks again for your response.

 

[Guest]

instructions, all one needs to do is share the (entire) hard drive over the
network giving read-write privileges to the other machine(s), then make a
shortcut to the application's executable file from the (networked) machine.

Two points:

A. If you need to share the app, then share the app's folder. Sharing the
entire HD exposes the computer to damage from simple explorer-mistakes,
malicious users and viruses on other computers.

B. In any case, VFP won't run like this, it needs to be installed onto the
client computer. When its setup is run, this puts several DLLs into the
Windows\System(32) folder. True, you might be able to get around this by
copying the DLLs to its own program folder, or to any folder in the Path, but
there is no guarantee this will work.

The database and code can of course be on a network share. If this is a set
as the working folder, then no changes to the code should be necessary.

The older versions of FoxPro (particularly DOS, and probably the 16-bit
Windows version) could be run from anywhere without installation.
Unfortunately that ability is rare on modern programs.