G
Gareth Grindal
I recently had some issues with Access97 running on a
netwrok drive.
We had recently moved from a server running NT4 to a
system running Windows 2000 with Terminal Emulation blah
blah...
anyway, it turns out that my datasource and the
subsequent software that manages this info [Pegasus
Opera - Yuk!] was mapped onto a dedicated network drive.
Now, my problem started when I figured what the hek, I'll
use Access 2002 becauses its shiny, new etc..
So I had to do a bit of *tweaking* with the 97 version as
2K + uses ODBC rather than Jet to connect to the FoxPro
data source (its been a long two weeks and I have been
the whipping for that time so please be gentle when
correcting by million mistakes).
So, any way I had to give up with that idea in the short
term because I was getting inconsistent record counts
when I exported my data (something to do with me having
to create queries for my range lists because of how the
source data is indexed and I could not get these lists to
order alphabetically - I know I know *whip*) so because
of the whip I had to revert back to the old method so I
could get my work done, then *fix* everything when I had
the spare time.
It turns out however, that, that we are running Access 97
run time on the network drive, so I could not modify any
part of my query.
And on top of that gem, when I *tried* to export the data
(150,000 records) it wants to take a *long* time, so long
that I went home and left it running and came back the
next day and it still did not finish!
So much screaming and tears later, I manage to frighten
the life out of IT and get them to wap on a copy of A97
on a server for me to see what was going on. And what do
you know, it works!
Turns out there were some issues with running Access on
the netwrok drive.
I am curious though as to the reasons why?
netwrok drive.
We had recently moved from a server running NT4 to a
system running Windows 2000 with Terminal Emulation blah
blah...
anyway, it turns out that my datasource and the
subsequent software that manages this info [Pegasus
Opera - Yuk!] was mapped onto a dedicated network drive.
Now, my problem started when I figured what the hek, I'll
use Access 2002 becauses its shiny, new etc..
So I had to do a bit of *tweaking* with the 97 version as
2K + uses ODBC rather than Jet to connect to the FoxPro
data source (its been a long two weeks and I have been
the whipping for that time so please be gentle when
correcting by million mistakes).
So, any way I had to give up with that idea in the short
term because I was getting inconsistent record counts
when I exported my data (something to do with me having
to create queries for my range lists because of how the
source data is indexed and I could not get these lists to
order alphabetically - I know I know *whip*) so because
of the whip I had to revert back to the old method so I
could get my work done, then *fix* everything when I had
the spare time.
It turns out however, that, that we are running Access 97
run time on the network drive, so I could not modify any
part of my query.
And on top of that gem, when I *tried* to export the data
(150,000 records) it wants to take a *long* time, so long
that I went home and left it running and came back the
next day and it still did not finish!
So much screaming and tears later, I manage to frighten
the life out of IT and get them to wap on a copy of A97
on a server for me to see what was going on. And what do
you know, it works!
Turns out there were some issues with running Access on
the netwrok drive.
I am curious though as to the reasons why?