multiuser database questions

[LAByerly]

I have an application running with an access 2000 database and VB6. There
are between 3 and 6 simultaneous users updating the data base. They keep
getting "the database has been placed in a state by an unknown application
that prevents it from being opened or locked" I assume this message is saying
that there are too many users accessing at the same time. Does anyone know
what settings I can change to get rid of this?? Would MSDE be better than
jet? Can you run MSDE on a windows 98 network??

All help is greatly appreciated

[ralph]

"LAByerly" <byerly@byerly.biz> wrote:
>
>I have an application running with an access 2000 database and VB6. There
>are between 3 and 6 simultaneous users updating the data base. They keep
>getting "the database has been placed in a state by an unknown application
>that prevents it from being opened or locked" I assume this message is
saying
>that there are too many users accessing at the same time. Does anyone know
>what settings I can change to get rid of this?? Would MSDE be better than
>jet? Can you run MSDE on a windows 98 network??
>
>All help is greatly appreciated
>

There are lots of reasons for this problem. Check this knowledgebase article
out first. It also includes suggestion for other articles for help.

http://support.microsoft.com/default...b;en-us;300216

[Note: when seeking troubleshooting help on MSAccess topics be aware that
you need to employ 2 or 3 separate 'filters' - "MS Access", "Jet Databases",
or "OLE DB/ODBC Jet drivers". Queries against one topic will often not return
the same results.]

For more information on going to MSDE...

http://support.microsoft.com/default...b;en-us;321518

IMHO on MSDE - if you are using any other database, or plan to use any other
database other than SQL Server and intend to keep your application small,
with few users, then don't bother. MSDE is just SQL Server Lite after all.
Moving to MSDE to resolved a configuration error, or poor programming decisions
is a very lame excuse to switch.

However, if SQL Server is your primarily database and your company's destiny
(with possibly .NET?) then immediately drop Jet and use MSDE - appreciating
the fact <g>, that by the time you write your second application - there
will be NO going back.

(Hey! Billy didn't get rich giving too much away, he got rich by giving a
little bit away... at a time. <g>)