Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

remote desktop substitute or VFP code

Status
Not open for further replies.

newtofoxpro

Programmer
Sep 16, 2007
301
IN
My Client has Win2003 server [PC1] with static IP. It works good with remote desktop [PC2]. PC2 is far away from PC1 but works good with remote desktop with static_IP via internet. My problems is

1) Printing to local Computer : PC1 has Lpt1 port & PC2 has Lpt1 Port the same printer driver installed at PC1 & PC2. Many times works. But PC3 is Laptop having USB port printing. It does not work.

2) Another Problem is Static IP is not hidden so third person can access data from anywhere. Most worst is all drive & data of PC1 is open to the world.

VFP8 has ability to use IP address followed by drive and dbf (\\xxx.xx.xx.xx\C\myfolder\mydbf.dbf ) But it is limited to local area network.

I am looking for CODE which can access only DBF via internet.
 
I am looking for CODE which can access only DBF via internet.

As to that issue I think you are out of luck. I don't know of any VFP utilities which will allow you to make a 'live' connection (Realtime Read & Write) to a data table via the web. Maybe someone else will be able to help with that. However even if you COULD get it working, the user would most likely experience SLOW performance.

REGARDLESS of that, the other issues/challenges you describe are all capable of being handled at the Network level by a knowledgeable Network Administrator.

You can limit the RDP access to only a limited number of external, authorized IP's to minimize the vulnerability to outside entities 'tip-toeing' around through your central system.

And the individual remote 'local' printers can be configured on a user-by-user basis.

Good Luck,
JRB-Bldr


 
However even if you COULD get it working, the user would most likely experience SLOW performance.


No, performance is good, this required high-speed connection.
 
PC2 is far away from PC1 but works good with remote desktop with static_IP via internet".

Sorry, don't quite understand, you seem to be saying that PC2 ... works good ... via internet, then you ask about code to access a DBF via the internet(?).

Does your App reside on the server, or on the local PCs with only the data on the server? I have an installation with the Apps local but data on a central W2003 Server, and 'home workers' access via VPN. As Mike says though, the real time speed is awful and depends so much on factors (eg broadband) out of our control, and you do have potential firewall and other access issues.
Rob
 
you can use a web server and read/write to dbf
like west-wind or FoxWeb

i use foxweb server..

you would have to develop in html/vfp hybrid..

that site is 100% pure VFP (with html ofcourse) and uses VFP9/FoxWeb

Ali Koumaiha
TeknoSoft Inc.
Michigan
 
As you got several alternatives, I second jrbbldr, you can solve the remote desktop security on the administrative level and while there are solutions to server vfp data via the web, they would involve application changes. The other solution not mentioned is extending the network via VPN. This again involves logging in to the PC from remote, but like RDP can be limited to the users.

But as you already have a remote desktop solution, you just need to tighten your security settings, so I end up with jrbbldr's advice again.

Bye, Olaf.
 
Rob, Sorry for complications,

1) PC1=Win2003 with static IP. Foxpro Software & DBF is installed at this machine. PC1 is at Head-Office.

2) PC2=Winxp with variable IP. Foxpro Software & DBF is NOT installed at this machine. PC2 is at Brach-Office(1). (100KM away from Head Office)

PC2 access PC1 via remote desktop and internet. Read/Write works good. PROBLEM IS PRINTING to local=PC2 machine. Many times prints & few times does not.

3) PC3=Laptop_Winxp with variable IP Foxpro Software & DBF is NOT installed at this Laptop. PC3 is at Brach-Office(2)

PC3 access PC1 via remote desktop and internet. Read/Write works good. PROBLEM IS PRINTING to local=PC3 machine where DOT-MATTRIX printer attached to this laptop via USB cables. IT DOES NOT PRINT.

I tried my level best to ask my question.

@Olaf : I understood that, data safety can be manageable.

If VFP use dbf like (\\xxx.xx.xx.xx\C\myfolder\mydbf.dbf ) this via internet then it is most easy way.
 
Ok, I'm clearer now on the setup. It doesn't sound like a VFP issue to me.
PC2 & PC3 access the data on PC1 via remote desktop, so then it will be PC1 'instructing' the local printers to print. It is effectively the same as sitting at PC1 and directing printer output to a printer attached to another PC.
Is PC1 configured to print to the relevant ports on PC2 and PC3, and are correct drivers installed on PC1?
When printing from your VFP app, do you use the PROMPT parameter to bring up the print dialog?
Can you print at PC2 or PC3 using other applications (eg MS Word), residing on PC1?
You say (PC2) "Many times prints & few times does not." - classic question, what is different on those occasions when it does not print?
Good luck.
Rob
 
If VFP use dbf like (\\xxx.xx.xx.xx\C\myfolder\mydbf.dbf ) this via internet then it is most easy way.

No, actually this has many difficulties:

1. A user is not logged in to a webserver, therefore you can't use windows file security to determine who could open a file. This issue may be solvable, but I can't tell you how, you'd need to host on IIS / Windows based server for sure.

2. There need to be some doors opened, which you normally won't open for the protocol VFP uses to read data is not TCP/IP only, so internet connections/ports are not sufficient for this kind of remote data usage.

Trust me, you don't want that, and you don't need that, beacause as you do remote desktop, you don't need any such usage of data, as CEMrob says, remote desktop is like sitting at the remote controlled pc, and thus you can use an application without any changes remotely, that is the big advantage of remote desktop or terminal services or something alike. What travels the line/internet connection via remote desktop is just the desktop, it's visual appearance and keyboard/mouse. You're just remote controlling a pc, apps don't even recognize they are used remotely.

Bye, Olaf.
 
@Rob, I should find my answer in your comments. Well thank you. Please give me some time to check this all.

@Olaf, you are right, while using foxpro I sould not find substitute of remote desktop. In fact, I am happy with Remote desktop till read/write data. If I solve Printing & Data security issue then it would be one of the best option for me.

Thank you.

My dream Application/Module is : If I installed My_Application at PC1(Server) as well as PC2(Client) both pc has internet connections. PC1(Server)'s My_App should produce some ID & Password which has to feed at PC2(Client)'s My_App and the PC2
would use PC1 data. Like teamviewer. (Please don't laugh)


"Possibility or impossibility doesn't depend on the size of our goal but on the size of our faith!
 
@Olaf: I'm not sure newtofoxpro is actually talking about hosting the app on a webserver. I thought the requirement is just to have some way of accessing data held at one terrestrial location from somewhere else (and print it).

@newtofoxpro: Ref your 'dream'- As I mentioned above, I have an app running in an office where the data is held on a central server running W2003 Server (your 'PC1') with a static IP. The app is not on that Server, it does not need to be. Within the office there is a LAN with a number of PCs, on each of which the app is installed, and they all access the shared data via common drive mapping. LAN security is outside the scope of the VFP app, but the app obviously has its own password/security features.

The office LAN connects to the outside world via a DrayTek Vigor Router with a static IP, which is enabled for VPN passthough; again, that and Firewall maintenance is not part of the VFP app.

Authorised persons working outside the office can access the server via VPN through the router and into the LAN; obviously the app is present on their home PC, laptop or whatever. Unauthorised access attempts to the DBFs have to get through the Router's security, then 'find' the server on the LAN and get past the server's security. Not impossible, agreed, but not easy.

The advantage of this system is that it is actually quite straightforward and relatively simple and cheap to set up but, as already stated, real time speed (or lack of it) is the big drawback. Having most processing, and temporary cursors or even DBFs etc handled locally helps, but ultimately there has to be a lot of data flowing back and forward over the phone lines.

Incidentally, there are no printer issues of the type plaguing you, because printing is completely local, or output is to networked printers in the office itself.

I really don't know if any of this is of use to you, but it works for me.
Rob
 
@CEMROB. WEll replace webserver with Domain in my previous post. With or without IIS involved, the remote client accessing data via an IP (xxx.xx.xx.xx) based path is not logged in as a windows account, so files would need to with public full access.

@both:
A connection made before that establishing a VPN tunnel would extend the LAN and make that possible.

@newtofoxpro:
A VPN would give you the possibility to let a local install make just the data access remotely. Then you can use whatever local printer, too. Cisco VPN client would be one such tool to establish a VPN tunnel.

But: Data usage via a VPN extended network is not nearly as stable as remoting the desktop, so staying with remoting is the better option. VFP uses quite some low level smb protocol and filesystem specifics to allow shared file usage, locks (manual or automatic), etc. So you better only have a LAN between client and your DBFs, not the internet. VPN does tunnel network packages via the internet in a way not noticable to any application, so they say... DBFs are not for world wide usage. VFP is no database server, that's the problem.

Teamviewer is a remote desktop alternative, and you only have a security issue, if you allow anybody to log in. You can restrict remote usage. But you don't need remote data access then, you don't even need to install a software on the second client connecting via teamviewer or remote desktop or citrix or whatever.

What you can combine is VPN tunnel and remote desktop. This is a good option to have a login additional to the remote desktop login and gives you full control over who can connect, who can establish a VPN tunnel. The stability of the connection does not matter that much, if it's just used for remote desktop.

If you in the end want to allow any user, then you're bound to make a web application of it, everything else is impracitcal and remoting your application has it's limits.

Bye, Olaf.
 
not logged in as a windows account
VPN tunnel
Teamviewer
Authorized persons
There need to be some doors opened
PROBLEM IS PRINTING to local=PC2/PC3 machine (a.k.a. support of local printing on remote users' workstations)
etc.


This whole posting seems to be related to Network configuration and/or other Windows requirements - NOT VFP related.

As such, a better and more focused resolution will probably come from another area within Tek-Tips (one that focuses on Network issues) or another forum altogether.

Once the various network issues are addressed/resolved, then if any VFP issues remain, we will be glad to help.

Good Luck,
JRB-Bldr

 
This whole posting seems to be related to Network configuration and/or other Windows requirements - NOT VFP related. "

I should QUIT from this thread and move myself to another area with in Tek-Tips where focuses on Network issues.

I should find some concrete solution to use VFP with internet. After that I can provide lot-of facilities to my clients.

Thanks & Best Regards.



"Some succeed because they are destined to; but most succeed because they are determined to!"
 
If you don't limit it to dbfs via internet, but Fox+Internet, remote desktop is in that range and in such discussions has most often won, if it's just about using a certain already finished app remotely. If you are at the start of the project, you can choose other options, including

FoxWeb
Active Foxpro Pages
Active Fox
West Wind Web and other tools by West Wind
VFP2IIS
FoxInCloud

But none of them is going the route to only put DBFs on the web. The closest would be implementing web services to access data via the internet only and otherwise work with a local installation of a foxpro app. But then again you'd have a two way storage engine for DBFs in direct,local use and adressing Webservices on the other side.

The best option to store data onyl in the internet is to make use of a sql server allowing remote access, eg SQL Azure, MS SQL Web, MySQL. SQL Azure or any "cloud" database is especially made for that, MySQL as the most widespread database for web apps is surely a web app, but mostly restricted to local useage of a webserver, not open for remote connections. That is possible but has security aspects you need to take into account.

That option is almost out for DBFs, as said, because it's a file, not a server. And all the aspects of locking are solved via the NTFS file system and SMB protocol, which only does work out via a inernet connection by means of openening too many doors, as it would be practical. That's why that option always loses in such discussions. Merly the apspect of latency via internet vs. LAN vs local DBF access makes it unbearable to use DBF via internet.

Thats why all solutions putting data on the web also put the logic to access that data to the web, including remotly available SQL Servers. See? They not only store the data, they also have a server there that receives the queries and executes them. And any of the above mentioned foxpro solutions do that, too.

Bye, Olaf.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top