Access warnings relating to "exclusive" mode

[kaleolani65]

I recently started a job at a medical staffing company, a database used to keep information was built by a lady there who has very limited Access experience (even less than me)

They run Access2k3, on WinXP desktops

The files and DB reside on the corporate server.

She complains that in the mornings the first person who opens the DB locks all others out, once they logout and the others log in everyone can begin working.
Through research I figure that the first person is opening the DB in "exclusive" mode therefore locking all others out.

1. How can I fix this "lockout" problem?

Some research says that the DB data should reside on the server, while the "frontend" should reside on the individual workstations.

2. Is this something that can be done after the fact?

Another problem is the caution box...

***Microsoft office access cant save design changes or save to a new database object because another user has the file open. To save your design changes or to save to a new object, you must have exclusive access to the file.***

3. Would the implementation of a DB users and groups schema help things?
For instance, setting having one DB admin and having the rest of the others set up as users.

The research I did online and in this forum helps a little, but most of it is over my head

Thanks in advance for any help...

[kaleolani65]

Sorry about the delay.
In about an hour I will post the output of Documenter, hopefully someone will be able to see where the change in field names is making the "enter parameter value" box pop up.
This may also give NeoPa a better idea as to the structure of the DB.

See if this helps anyone...


And the DB is about 4.5MB
When we fire up this table it complains and tells me to "enter parameter value" in the count section

Table: Multi-Markets Plans Page: 1
Properties
DateCreated: 1/30/2007 9:44:47 PM DefaultView: Datasheet

GUID: {guid {86649018-7B35- LastUpdated: 2/13/2007 9:12:02 AM

4842-8CF3-

NameMap: Long binary data OrderByOn: True



Orientation: Left-to-Right RecordCount: 10

Updatable: True

Columns



Name Type Size



Count Long Integer 4

AllowZeroLength : False



Attributes: Fixed Size

CollatingOrder: General

ColumnHidden: False



ColumnOrder: Default

ColumnWidth: 690

DataUpdatable: False

DecimalPlaces: Auto



DisplayControl: Text Box

GUID: {guid {364300D6-9E93-4705-B259-A06B33DE35DE}}

OrdinalPosition : 0



Required: False

SourceField: Count

SourceTable: Multi-Markets Plans


Multi-Market Plans Memo -

AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: 1935

DataUpdatable: False

GUID: {guid {7CA6A057-468C-46F0-B9DF-ABDFE24D19A7}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 1

Required: False

SourceField: Multi-Market Plans

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

ARIZONA Memo -
AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {194EDA17-7A32-4493-A490-D39A491D5EF8}}

\\tcma-med.com\public\ ITDevelopment\M SS Tracking Wednesday, February 14,

Table: Multi-Markets Plans Page: 2

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 2

Required: False

SourceField: ARIZONA

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

FLORIDA Memo -
AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {BF8F0C0E-B23A-40C6-8DF5-1403804819C6}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 3

Required: False

SourceField: FLORIDA

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

NEVADA Memo -
AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {B8535537-3051-457C-BF67-367A6369E33E}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 4

Required: False

SourceField: NEVADA

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

TEXAS Memo -

AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {F7E268F2-9EB5-4706-8AC6-729DBC8578B9}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 5

Required: False

\\tcma-med.com\public\ ITDevelopment\M SS Tracking Wednesday, February 14,

Table: Multi-Markets Plans Page: 3

SourceField: TEXAS

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

UTAH Memo -

AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {99F49EDD-CED7-49E2-8DC4-192F6AFAFFCE}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 6

Required: False

SourceField: UTAH

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

LOUISIANA Memo -
AllowZeroLength : True

Attributes: Variable Length

CollatingOrder: General

ColumnHidden: False

ColumnOrder: Default

ColumnWidth: Default

DataUpdatable: False

GUID: {guid {9A8E93FC-564F-4CA7-A2D2-7A426BA9EE93}}

IMEMode: 0

IMESentenceMode : 3

OrdinalPosition : 7

Required: False

SourceField: LOUISIANA

SourceTable: Multi-Markets Plans

UnicodeCompress ion: True

User Permissions

admin Delete, Read Permissions, Set Permissions, Change Owner,

Read Definition, Write Definition, Read Data, Insert
Data,

Group Permissions

Admins Delete, Read Permissions, Set Permissions, Change Owner,

Read Definition, Write Definition, Read Data, Insert Data,

Users Delete, Read Permissions, Set Permissions, Change Owner,

Read Definition, Write Definition, Read Data, Insert Data,

[kaleolani65]

Well,
I copied over the DB into another area so I could work on it. I pulled up the form which was having the "enter parameter value" problem in the count column. I looked at it in table view (or the one that looks like a spreadsheet) sorted the values in count in descending order, shut it down, fired it up and no complaint this time? I guess for the time being it's fixed.

When I tried it on the real file it would not allow me to save design changes since i was not the sole user of the DB, how would I find out who I need to log out so that I can get full control?

[NeoPa]

See if this helps anyone...


And the DB is about 4.5MB
When we fire up this table it complains and tells me to "enter parameter value" in the count section

{Loads of MetaData}

Right,
The files too big to e-mail to me (that was the reason for the question).
However, try renaming the field [count] to something else (as Count() is a function and therefore a reserved word). Count will work in most circumstances but clashes are possible.

From this MetaData, is it true that the database has only one object in total - a table called [Multi-Markets Plans]? Or possibly, did you just forget to include any of the other objects?

[NeoPa]

Well,
I copied over the DB into another area so I could work on it. I pulled up the form which was having the "enter parameter value" problem in the count column. I looked at it in table view (or the one that looks like a spreadsheet) sorted the values in count in descending order, shut it down, fired it up and no complaint this time? I guess for the time being it's fixed.

When I tried it on the real file it would not allow me to save design changes since i was not the sole user of the DB, how would I find out who I need to log out so that I can get full control?

As no-one else could be accessing it at the same time then this would be expected.
Having a Form to open implies that there is more to the database than just the simple table listed earlier.
Type out the .LDB file to see if you can see anyone else logged on.

[kaleolani65]

As no-one else could be accessing it at the same time then this would be expected.
Having a Form to open implies that there is more to the database than just the simple table listed earlier.
Type out the .LDB file to see if you can see anyone else logged on.

I played around with it and found that if I sorted the file in datasheet view from lowest to highest the DB stopped complaining about the "enter parameter value"
also when I looked at the DB in form view (I think it was form view) the count column was offset by two clicks so I repositioned through the drop down box and it seems to work.

[NeoPa]

Glad you got it sorted - I can't say I understand why - but who cares eh?