Replication vs "Smart Client" remote connection to database

Hello everyone
I have a big project and want the right architecture

My question is...
can you easily create a sort of smart client to
use windev apps locally but access the DB across the web to a central server?
or is this a dumb idea...

I Just purchased windev and Fabrices tutorial course, all very great.
Have learnt (still a long way to go) alot

I need help to decide how my user base (upto 100 little businesses) should connect to my central database in my app.
First the users are small businesses with 1 - 5 pc's on a small network, or they are just a little guy with a single pc.

I work with them, helping them with their marketing.
They update their info onto the database.
I update my end with schedules, plans, contact details
new advertising copy etc.

Currently Im using a web app to do this, but I like the idea of giving the
benefits of a full windows app.

Obviously we need to be connected to the same database
so we can work together.

My options are...
1) webdev and a internet server with hyperfile across the web

2) windev with replication with remote hyperfile DB

3) Or a "smart" client with hyperfile across the web.
I know true smart clients cache the data on their local machine, and work with local copies before "sending" changes. But do I really need to do this?
Cant I give all the benefits of a windev application to my users,
and get data from a remote connection across the web to a server?
Or am I dreaming?

After Fabrices tutorial on replication, to be honest it scares me.
Its a big job.
I like the idea of avoiding replication and using windev to connect remotely

However I have no idea if this is a viable option?
Is anyone else doing this type of app in windev?
Is it going to be more complicated than replication?

As Im a lone programmer who programmes apps for my own use
, my choice is always to keep it simple,
use standard ways of doing things, And get a job done as fast as possible.

I dont try to be "clever", as I cant afford months of developement.
This is why Ive choosen windev over .Net.

I have been programming in foxpro and vb6 for 15 years
and I prefer to buy frameworks with all the plumbing in place
so i can work on the fun stuff. leaving the complex stuff to experts.

Fabrice, if your reading this, I did get your reply about replication
and all that is possible in this area, thank you.

So in summary, can you easily create a sort of smart client to
use windev apps locally but access the DB across the web?
Or is a webdev app probably a smarter option?

Regards James
New Zealand

Hi There,

Why not host your own Terminal Server, Then give the users RDP access only to the app.
You can do this remarkably easily and cheaply by using XPunlimited.

You can just write the app in a very standard way, The difference is that it all runs on your server colocated at an ISP.

There are of course a couple of compromises here...
Printing becomes and issue, but it is easily solved by using Thinprint for XP Desktop, (90 Euro's - only 1 licence needed if using XPUnlimited)

Clipboard support is slightly limited.

This is a strategy that has been used by many people doing what you want to do very successfully.

Cheers

Bosh

Hello James...

To complete the previous answer (which is certainly a very viable option, and perhaps the simplest one to implement)...

I have seen windev app designed to access HF DB accross the web. This architecture has several consequences:

1. Slow data access (whatever you do, your data has to go through the web, with all the routing and delays it entails), which means that you are not giving your user the FULL advantages of a windows app, as the screen are displaying fast, but data access is much slower than normal

2. You need to design your app for that:
- limit data access to the minimum possible
- forget tables linked to a FILE (each time you scroll down, you need to go accross the net to get the next record, which gives VERY sluggish tables
- Work mainly (if not only) with queries, and design them (and therefore your app) to return SMALL amount of data
- and so on...

Now if you look at the other proposal you already got, you will AGAIN NOT give your users the full advantage of a WinDev app, as in that case Terminal server will have to send the screens through the web, which will give a sluggish display too...

So the only real solution to get all the advantages you want is to replicate the data, either with a timed replication (every 5 minutes, every hour, etc) or with a 'quasi real time one' (each time you do a data access locally, a second process access your remote data base and update it...

It's certainly more complex to implement, no question about that, but I do no think that there is another answer to all the requirements of your question

Best regards

Thanks Bosher & Fabrice

You have both definately given me something to think about.
I hadnt thought about terminal services at all.

Had a meeting with my tech company today and discussed the pros / cons of each idea.

I believe I understand the restrictions to my problem now.
I need to do more research into the responsiveness of terminal services
at various connection speeds. And review the documentation on replication hxxxx commands. Plus review Fabrices tutorial on replication again .

I comes down to the meeting the users expectations of performace
in a cost effecient way
while meeting time schedules...

Thanks Again

James

Hi All,

With regard to terminal services, it is definitely a viable option. And we've figured out away around the common printing issues by developing our own method printing which is incredibly simple and I'm shocked that no one else started doing it.

The whole idea started with me writing a wrapper around the msrdp activeX. From there we went crazy with various features that fill the gaps of problems with TS type clients.

Cheers!
Ken

Hey Ken,

We'd be interested to know a bit more about your rdp wrapper..
Any chance of sharing more info?

Cheers

Bosh (Bob)

Read this book "Apress - Pro SQL Server 2008 - Service Broker" for solution and ideas.

Message forwarded from pcsoft.us.windev

Hi Ken and Bob,

I'd be interested in your wrapper also Ken. We are using XPUnlimited and it works great but we do have some printing hassles particularly with older applications that insist on printing to a local printer.

Thanks for the Thinprint tip Bob

Thanks

Kevin

Hi Kevin and Bob,

I wrote the wrapper, however, I wrote it for a company that I have been doing work for, for the last year or so. Let me see if they are interested in commercializing the product.

Cheers!
Ken