Then what you can do, is to copy the file from the location to a
local client, when ever the application opens, and then the user can
do it again whenever he feels like it by pressing a upload button.
Quite simple. And the database would be on a file server, and
everyone would have a local copy.
Ethernet traffic would be a killer otherwise.
And as for using Access file as a server, there are just so many sad
stories around.
Trausti
On Jan 7, 2007, at 11:12 AM, Giovanni wrote:
Ruslan thanks for your reply.
I understand and it is not like I have not mention it to them but
they dont care for a client-server setup. In my client situation,
having a server will not be possible.
Ruslan Zasukhin wrote:
From: Giovanni <[EMAIL PROTECTED]>
Date: Sat, 6 Jan 2007 22:17:45 -0800
I get the point.=20
Does anyone have a solution that does not require an app running
as server?
Hi Giovany,
Please contact me off-list to describe again your task.
I did not follow up this thread deeply.
Actually, you as developer not always should listen your user.
He want "just to have files on server computer"? Like do MS Access?
Access was designed in 1990. So may be your user have stick in
that years?
:-)
---------
It can be good chance talk with him and get CLEAR answer why he so
much do
not like idea of install db server?
Waste of resources??? This is not a reason today.
or your user uses i386 computer with 16Mb of RAM as SERVER? :-)
unlikely....yes?
WASTE OF RESOURCES? Then please answer me: WHICH RESOURCES you
waste?
In fact this is not true!!
With DB SERVER you SAVE resources!
Because it is WITHOUT DB SERVER:
you start press network traffic a lots,
you start press RAM of all N client-computers around.
you start eat CPU of N client computers.
If count TOTAL, without DB server -- you REALLY waste resources.
Ahhh, what about time? I mean time of N users which seat on client
computers
and wait for answers? Does their TIME of LIFE (okay WORK TIME) is
a resource
which should not be wasted? IMHO this is PRIMARY resource we all
do have.
:-)
Btw, we know see nice wave of back-switchers from "REAL SQL" and
testers of
"REAL SQL Server" back to Valentina. One developer have point: on
REAL SQL
Server queries for my 1GB+ database take up to 2 minutes. For
Valentina they
go under one second.
Count time of WAIT for 4-100 users around possible DB solution,
and ask self
where is REAL waste (per day/month/year) of worker-resources :-)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
