Can't add new record when not logged in to Windows XP as an Admin

[OpethRULES]

I am new to Access and have never made an application in my life so
bear with me. Here's my issue: I have a very small Access 2003
database with the backend residing in a folder on a server and the
front end on each user's desktop. The intended users of my application
have been given enough privileges to enter and read data in that
folder (I've even tried giving them Full Control). When I log into
Windows on the network, as an administrator, my .mde application works
perfectly-my form pops right up when I start the app and I can add and
view data as intended. However, when I test my .mde application and I
log into Windows on the network as a user of my application (no
administrative rights) I get an error message when I start the app.
"This recordset is not updatable" appears in the lower left corner and
the dialog box says "...You can't go to the specified record". After I
'OK' through the dialog box my form appears but is completely blank
(no fields) except for the background color. The underlying table of
the form displays no active or "queued up" record for data insertion.
The desktop version of the database works fine when I'm logged in
under a user account-it is the split version that will not work. This
doesn't have anything to do with Access security because I can log
inot windows as a user and then log into Access as an Admin, and it
still doesn't work. Doesn't sound Access related, but I don't know
much about this. I've searched a ton of forums without finding anyone
with this problem anywhere! Please help! Thanks

 

[UsenetUser]

I might be on the wrong track so please no whining if it turns out to
be a waste of time, but if you like, I will take a shot at this.

- Where is the query that gives the error - on the front ends where it
should be or the back end?

- You say you gave the users full control on the back end, but did you
check to see if it was in effect by trying to write data to that
folder as one of them over the LAN, because it can take time or a
reboot for the permission change to be effective.

- You mention a form does not populate. is that form based on a table
or a query?

- What happens if a user (not admin) tries to open the backend
directly?

Oh, some line breaks would make your posts MUCH easier to read!

 

[OpethRULES]

Thank you for replying to my post-sorry for the crappy formatting.
I'll answer your questions as you posed them:

- Where is the query that gives the error - on the front ends where
it
should be or the back end?

There are no queries in my db yet.

- You say you gave the users full control on the back end, but did
you
check to see if it was in effect by trying to write data to that
folder as one of them over the LAN, because it can take time or a
reboot for the permission change to be effective.

I just tried doing this with a .doc and it was read-only even with
full permission. The head of IT says that I should never have to
reboot our server when permission changes are made.

- You mention a form does not populate. is that form based on a table
or a query?

The form is based on a table.

- What happens if a user (not admin) tries to open the backend
directly?

The user can open the back-end, but in read-only mode.

Thanks for your assistance.