dBASE Plus, Novell, odd errors

Greetings.

This is a weird one, to me. I hate dealing with situations where all 
works fine in one place, but not in another.

My client has a routine that imports his old DOS application's data to 
the Windows version I've been working on for sometime (the import is 
necessary, as changes are made in the data, and so on ...).

On a standalone computer this works perfectly, runs through the process, 
all is well.

On the small Novell network he's also got the application on, it errors 
out somewhere along the line. Sometimes it is in the rebuilding index 
routine (from the dUFLP, generated by CreateReindex.prg). Sometimes it 
is elsewhere.

The errors are often "Database Engine Error: Access to table disabled 
because of previous error", This is after rebooting the machine 
sometimes, and the error shouldn't be there (this has always occurred 
for me if some other error did occur, but if I rebooted, the error went 
away).

It's getting to the point of serious frustration, as he needs to import 
the data from the DOS app to do some parallel testing of the system 
against the older DOS app to make sure the data is being processed 
correctly.

Ultimately this will not be an issue, after the final time he does the 
import (after deciding the app really is ready to go completely live). 
However, until that time, I was hoping people who've worked specifically 
with Novell networks and dBASE could tell me anything that I can pass 
along to his network support guy that might help with this kind of 
issue. (Anything dealing with locks, settings for Novell, the BDE, 
whatever might be needed ...)

Thanks. (Sigh)

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

In article <vdz3z3YnIHA.940@news-server>, dbase@_nospam_goldenstag.net 
says...
> Greetings.
> 
> This is a weird one, to me. I hate dealing with situations where all 
> works fine in one place, but not in another.
> 
> My client has a routine that imports his old DOS application's data to 
> the Windows version I've been working on for sometime (the import is 
> necessary, as changes are made in the data, and so on ...).
> 
> On a standalone computer this works perfectly, runs through the process, 
> all is well.
> 
> On the small Novell network he's also got the application on, it errors 
> out somewhere along the line. Sometimes it is in the rebuilding index 
> routine (from the dUFLP, generated by CreateReindex.prg). Sometimes it 
> is elsewhere.
> 
> The errors are often "Database Engine Error: Access to table disabled

> because of previous error", This is after rebooting the machine 
> sometimes, and the error shouldn't be there (this has always occurred 
> for me if some other error did occur, but if I rebooted, the error went 
> away).
> 
> It's getting to the point of serious frustration, as he needs to import 
> the data from the DOS app to do some parallel testing of the system 
> against the older DOS app to make sure the data is being processed 
> correctly.
> 
> Ultimately this will not be an issue, after the final time he does the 
> import (after deciding the app really is ready to go completely live). 
> However, until that time, I was hoping people who've worked specifically 
> with Novell networks and dBASE could tell me anything that I can pass 
> along to his network support guy that might help with this kind of 
> issue. (Anything dealing with locks, settings for Novell, the BDE, 
> whatever might be needed ...)
> 
> Thanks. (Sigh)
> 
> Ken



Ken,

"Database Engine Error: Access to table disabled because of previous 
error" makes me think "corruption".

Which version of Novell is he using? Do the client PCs have the most up-
to-date version of the Novell client? In years gone by, the Microsoft 
client for Novell networks was slow and prone to problems.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

Geoff Wass [dBVIPS] wrote:
> 
> Ken,
> 
> "Database Engine Error: Access to table disabled because of previous 
> error" makes me think "corruption".

I'm pretty sure it's not corruption. I've seen this error occur at 
times, and if I rebooted the machine, it went away. It happened if some 
error happened in a process, and the BDE kept a lock on something 
somewhere, the only solution at that point being to reboot.

> Which version of Novell is he using? Do the client PCs have the most up-
> to-date version of the Novell client? In years gone by, the Microsoft 
> client for Novell networks was slow and prone to problems.

I'll ask ...

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

Ken Mayer [dBVIPS] wrote:
> Greetings.
> 
> This is a weird one, to me. I hate dealing with situations where all 
> works fine in one place, but not in another.
> 
> My client has a routine that imports his old DOS application's data to 
> the Windows version I've been working on for sometime (the import is 
> necessary, as changes are made in the data, and so on ...).
> 
> On a standalone computer this works perfectly, runs through the process, 
> all is well.
> 
> On the small Novell network he's also got the application on, it errors 
> out somewhere along the line. Sometimes it is in the rebuilding index 
> routine (from the dUFLP, generated by CreateReindex.prg). Sometimes it 
> is elsewhere.
> 
> The errors are often "Database Engine Error: Access to table disabled

> because of previous error", This is after rebooting the machine 
> sometimes, and the error shouldn't be there (this has always occurred 
> for me if some other error did occur, but if I rebooted, the error went 
> away).
> 
> It's getting to the point of serious frustration, as he needs to import 
> the data from the DOS app to do some parallel testing of the system 
> against the older DOS app to make sure the data is being processed 
> correctly.
> 
> Ultimately this will not be an issue, after the final time he does the 
> import (after deciding the app really is ready to go completely live). 
> However, until that time, I was hoping people who've worked specifically 
> with Novell networks and dBASE could tell me anything that I can pass 
> along to his network support guy that might help with this kind of 
> issue. (Anything dealing with locks, settings for Novell, the BDE, 
> whatever might be needed ...)
> 
> Thanks. (Sigh)
> 
> Ken

 From my client:

"   the client PC's use Novell's own, not mfst. Novell
was last updated about 10 months ago. The version is
"novell enterprise open server -powered by netware"

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

In article <h8YRT5inIHA.1516@news-server>, dbase@_nospam_goldenstag.net 
says...
> Geoff Wass [dBVIPS] wrote:
> > 
> > Ken,
> > 
> > "Database Engine Error: Access to table disabled because of
previous 
> > error" makes me think "corruption".
> 
> I'm pretty sure it's not corruption. I've seen this error occur at 
> times, and if I rebooted the machine, it went away. It happened if some 
> error happened in a process, and the BDE kept a lock on something 
> somewhere, the only solution at that point being to reboot.
> 
> > Which version of Novell is he using? Do the client PCs have the most
up-
> > to-date version of the Novell client? In years gone by, the Microsoft

> > client for Novell networks was slow and prone to problems.
> 
> I'll ask ...
> 
> Ken


Ken,

If that's the case, would deleting the PDOXUser.lck file help?

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.