prprogrammer
Programmer
HI I have a Windows VB Aplication in my Loal I want to know if exist some service o software to run this application over the net without changing it to webbase programing....
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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Run VB Application Over the net
- Thread starter prprogrammer
- Start date
- Status
dilettante
MIS
When you say "Windows VB Application" I assume you mean a regular old forms-based standard EXE project.
It wouldn't need to be web based. You just partition the application into a multiuser server-side piece and a fat-client GUI piece. Then glue the ends together with whatever fits your purpose.
Otherwise you'd need to use something like Terminal Server to provide remote desktops to users.
About the only other option is to use some sort of remote-database technology, like having your existing application sit on every desktop and connect to a SQL Server, Oracle, etc. database over the 'net. These are hard to secure without using a VPN though and the network traffic levels can be problematic.
Everything but a "remote control" type of technology (Terminal Server, VNC, etc.) means the user has to install application code though.
Even remote desktop approaches may require a little application rework to make sure it operates properly in a multi-user world. Temporary file collisions, registry entries for persistent per-user settings, etc. must be accomodated. If there is just one user though it should work as is.
To get your feet wet without hassle I'd try Win XP Remote Desktop Sharing. If you want to test it out with Windows desktop OSs older than XP (Win2K Pro, NT 4 Desktop, Win9x) you can always use NetMeeting Remote Desktop Sharing - which isn't bad for occasional use over a LAN.
It wouldn't need to be web based. You just partition the application into a multiuser server-side piece and a fat-client GUI piece. Then glue the ends together with whatever fits your purpose.
Otherwise you'd need to use something like Terminal Server to provide remote desktops to users.
About the only other option is to use some sort of remote-database technology, like having your existing application sit on every desktop and connect to a SQL Server, Oracle, etc. database over the 'net. These are hard to secure without using a VPN though and the network traffic levels can be problematic.
Everything but a "remote control" type of technology (Terminal Server, VNC, etc.) means the user has to install application code though.
Even remote desktop approaches may require a little application rework to make sure it operates properly in a multi-user world. Temporary file collisions, registry entries for persistent per-user settings, etc. must be accomodated. If there is just one user though it should work as is.
To get your feet wet without hassle I'd try Win XP Remote Desktop Sharing. If you want to test it out with Windows desktop OSs older than XP (Win2K Pro, NT 4 Desktop, Win9x) you can always use NetMeeting Remote Desktop Sharing - which isn't bad for occasional use over a LAN.
Homersim2600
Technical User
It's unfortunate that Remote Desktop can only handle 2-users at single instance. I would suggest that Prprogrammer look into an ASP page, it is similar to coding in VB, and there is plenty of information on the Net to get you started.
"As far as the laws of mathematics refer to reality, they are not certain; as far as they are certain, they do not refer to reality."--Albert Einstein
"As far as the laws of mathematics refer to reality, they are not certain; as far as they are certain, they do not refer to reality."--Albert Einstein
dilettante
MIS
Well, if the remote desktop concept works one can always move up to full Terminal Services under Win2K or Windows Server 2003. WinXP's RDS is simply a throttled version of TS as far as I can tell.
I agree that application rewrite is probably the right answer in most cases though.
I agree that application rewrite is probably the right answer in most cases though.
- Thread starter
- #5
- Status
Similar threads
- Locked
- Question
- Locked
- Question