on-site customers will be constantly accessing these files. This means that
he will have to have a dedicated phone line or upgrade to dsl in each of his
stores. Since the information only changes twice a year he would rather (and
it does make sense) just replace the CD.
Ideally it should be a self-extracting app with all the data safely
encapsulated within.
gil
-----Original Message-----
From: Tom Kitta [mailto:[EMAIL PROTECTED]
Sent: Friday, January 02, 2004 12:32 PM
To: CF-Talk
Subject: RE: OT- making a windows based app
-- This should be a stand alone app, ie: neither IIS nor apache
should have to be installed on the computer; and for security reasons
the db should not be in an easily accessable file where employees
could just download it.
[Tom Kitta]
If the file resides on user's PC it is hard to make it hard not to be
downloadable by the end user short of encrypting the contents and making
any
download useless. You may take a look at MS SQL desktop engine, it has
some
limitations like speed and DB size (or table size? Under 2G anyways).
I am far for being knowledgeable about writing Win based applications, but
it seems that it would be easier and cheaper to do it as a web based
solution. Also, any updates will be automatic when using a central DB
server. I think the web is the way to go as far as informative
applications,like catalogs, are considered for development .
TK
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
