When I referred to the network being slow, it wasn't an Access problem, it
really *was* a network problem. I supported 3 applications that I wrote
with 3 different Access databases. I'm in California; I supported one here,
and two in the Midwest. To make it run as fast as possible, I put the two
databases used by the MidWest users in the MidWest.
When I wanted to open one of those, it took at least 2 minutes just to open
the frickin' database by double-clicking on it. That's right, just open it,
not run anything. As I tend to be impatient with computers, it was very
frustrating, but nothing I could fix.
So I think I had problems because of the network issue, and the state of
the database would be different when I started copying it versus when it
was in the middle or at the end. Once or twice in mid-day when network
traffic was at its highest, I couldn't even copy it in place, or to a
different folder in the MidWest even. Grrrrrrr.
It didn't happen enough to be a major issue, it was just an annoyance.
Your setup sounds really interesting; sounds like a fun project to work on.
I used to caddy for my father when I was young, and I have to say, golfers
take themselves and their game way too seriously. On the bright side, I
made a fortune (well, it was a fortune at that age) collecting golf balls
off the bottom of the lake and selling them to the clubhouse, although at
times it was dangerous work. Fore!
As for this:
P.S. Being nibbled to death by ducks would be a 'fowl' way to die, I must
admit... :) OK...OK... no stones....
Grooooan. I guess I asked for that. I could respond by calling you a turkey
or something silly like that, but I should resist. I don't want to crow
about my ability to pun, or have you think I'm going quackers.
Robin S.
-------------------------------------------------
"Bruce W. Darby" <kr******@atcom cast.netwrote in message
news:-6************** *************** *@comcast.com.. .
Well, from where I work, as the supervisor of a small tech support
department, yes, we should be able to copy it. We have a business
relationship with a company that markets a GPS system for golf carts.
That system is designed to keep our software alive and kicking, which
means that the .mdb is locked and cannot be modified or moved, etc. If we
need to have the course upload the database to us because of a problem,
then making a copy of it to the desktop, then uploading it to our web
server is the only way to do it without shutting down the GPS system.
Shut down the GPS system on a day when the course if filled with players
using that system to keep their scores can result in a VERY bad day for
the course. :) I've never seen a 'copy' operation lose or corrupt data in
the .mdb and I've been using this copy method at least three times a
week. I 'have' seen the slowness that you indicate when the location of
the database is not within the same building as software running the
application. Seems like anything more than about 'across the parking lot'
causes Access to slow down to a crawl.
Bruce
P.S. Being nibbled to death by ducks would be a 'fowl' way to die, I must
admit... :) OK...OK... no stones....
"RobinS" <Ro****@NoSpam. yah.nonewrote in message
news:qe******** *************** *******@comcast .com...
>Yes, it *can*, but should it? I have had problems with that
in the past. I've gotten "locked" messages a couple of times,
and sometimes it appears that data being updated was lost.
Maybe it was because the network at the company where I worked
was soooooooooooooo o slooooooooooooo ooooow. Accessing information
across the network was like being nibbled to death by ducks.
