access database on novell netware 4.11

I have an access database(with around 90 MB size) and it works fine when I run it in my win95 pc. But when i compied the database to a newtware 4.11 server and run some form from it, it starts and it gets stuck, every time. I checked the novell site and it is written there the problem can be with my netware client version and they suggested to upgrade my netware client to version 3.2. I did that but still nothing changed. What can be the problem?Please answer this as soon as you can cause I have to run it today.
Thanks
LVL 4
oumerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tcullerCommented:
There are some sticking points between Access and Novell.  There can be even more if you are doing a client-server setup and the Users PC has Win 95 as their operating system!

You weren't specific as to what was going on when it "got stuck", but I will relate a war story, and if it matches, you can check for the same thing:

I was called in to fix a database in a company which had Access for the shared back end and also on the front end, through a Novell Network.  A process which had always run, had gotten slower and slower and then stopped, freezing Access, but giving no error message...

I found that the process that was running was bringing a large, updatable recordset over the network.  Even though Access handles its own recordlocking for just such a thing, Novell was inserting itself in the middle without being asked.  It has a maximum number of recordlocks setting, which if it is reached, just stops your process, WITHOUT LETTING YOU KNOW!

I had to have the LAN Mgr check his Administrator Log (whatever it is called) to see if there were any errors logged at the date and time that Access had gotten stuck- and there it was "Maximum number of record locks exceeded".  

The solution is to increase the settings.  Recommended settings can be done based on the number of records you know you will be processing, or look for recommended settings on the Microsoft website, using the keywords Novell and Recordlocks.

The other problem I have had is with Access-SQL Server through a Novell Network, where it handles the connections, or sessions differently than Microsofts programs...

Hope this helps you to investigate your problem,

Tim
0
JimMorganCommented:
The log file on the Novell server is the System Error Log.

The default lock setting in Novell is 1,000 locks.  Sounds like a lot but considering every 2K page is considered a lock, it runs out in a hurry for a big file.

The maximum lock setting is 10,000.  I normally use around 4,000.  Whatever setting the Novell Administrator sets for you, be sure that you change the permissable locks for the DB to the same setting.

BTW, I use the default Netware client that comes with Microsoft.  It may not be as fast but it sure is a lot easier to maintain and is very reliable.

It also sounds as if you have an all inclusive DB.  If the DB is split with Data on the server and the Program with all other objects on the local workstation, you will probably find that the problem goes away.  A lot of the locking overhead that you are seeing is being done by Jet inside the database itself.  When you are linking to tables in a server side DB, all the overhead is still kept on the local DB and locking problems go way down.

Jim
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JimMorganCommented:
Tim:  I don't know why I was given the answer.  I was just trying to back you up with a little more information.

Jim
0
tcullerCommented:
Jim,

     It's not about points, it's about helping people... If we helped him it's a good save, and I really like working with you as a team!

Tim
0
JimMorganCommented:
Tim,

Thanks.  Look for a little something in your stocking.

Jim
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.