By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,165 Members | 853 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,165 IT Pros & Developers. It's quick & easy.

Problems networking Access

P: n/a
Greetings all,

Here's my problem...

I've built a small Access database that I placed on my server. I have
one workstation connected to the database.

The folder that the database is in on the server is shared and I've
mapped the path to the database on the workstation.

The advanced tab of the database options are set to:

Default open mode - Exclusive
Default record locking - Edited record
Open databases using record-level locking is checked

The database is also split, the workstation has a frontend which is
linked to the backend on the server.

When I enter records into the database from the workstation, they do
not appear on the server. To be able to see the newly added record on
the server I have to close the database then re-open it to see the new
record. The same problem exists if I attempt to add a new record on the
server after one has been added to via the workstation, I can't save
the new record.

I'm a little confused as to why this is happening. Should I not use the
database on the server to view and edit records? Is there some
additional step I need to take in order to network the database
properly?

I would appreciate any suggestions, because from what I know about
Access the setup I'm using should work.

Thanks,

John

May 4 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I think that the record is still dirty when you are checking the BE which is
why it is not appearing. Create your new record and then navigate to another
record and then back again. By moving to a different record and back again,
it will save it (Dirty = False). Open up the BE and the record should be
there.

See how that works.

Mark

<jg****@gmail.com> wrote in message
news:11**********************@u72g2000cwu.googlegr oups.com...
Greetings all,

Here's my problem...

I've built a small Access database that I placed on my server. I have
one workstation connected to the database.

The folder that the database is in on the server is shared and I've
mapped the path to the database on the workstation.

The advanced tab of the database options are set to:

Default open mode - Exclusive
Default record locking - Edited record
Open databases using record-level locking is checked

The database is also split, the workstation has a frontend which is
linked to the backend on the server.

When I enter records into the database from the workstation, they do
not appear on the server. To be able to see the newly added record on
the server I have to close the database then re-open it to see the new
record. The same problem exists if I attempt to add a new record on the
server after one has been added to via the workstation, I can't save
the new record.

I'm a little confused as to why this is happening. Should I not use the
database on the server to view and edit records? Is there some
additional step I need to take in order to network the database
properly?

I would appreciate any suggestions, because from what I know about
Access the setup I'm using should work.

Thanks,

John

May 4 '06 #2

P: n/a
>Default open mode - Exclusive

The above should be set to shared...

The database is also split, the workstation has a frontend which is
linked to the backend on the server.
Good, that is the recommended setup.

When I enter records into the database from the workstation, they do
not appear on the server.


How are you testing the above? A form should be loaded to one record...you
exit the form (and thus save the record). You are then back to some type of
prompt the user for the next record to work on. If you just open form to a
large table of records, that form have to be told to re-load the records
(so that is can see other reocrds added by other people).

A good approach is to build some type of search form, such as

http://www.members.shaw.ca/AlbertKal...rch/index.html

So, ask/display the records you are searching for. If you do this, then you
eliminate the issue/problem of having to re-load up a form with a LARGE
number of records in the process, and your appcation will performance much
better.

You should not have to exit the application, but you certainly have to close
the form, or issue a requery to that form to see new records added. As
mentioned, if you change your design to ask for what records to view first,
then others peoples work will be available if you open up a form to these
newly added records....

And, if you are just testing by opening the back end direclty, you will have
to close, and then re-open a table to see the newly added records.

Of course, users would never see, or edit a table direct..but just a like
form, you do have to close, and then re-open the form to see records added
by other people.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
May 5 '06 #3

P: n/a
That sounds logical, I didn't even think of that. I suppose I could
also requery the table, which would do the same thing. That way it
world work on the server and workstation(s).

I'll keep you posted on this.

Thanks for your input,

John

May 5 '06 #4

P: n/a
Hi Albert,

Thank you so much, I was testing it by closing and re-opening the form.
If I requery the problem is solved. I like your idea about using a
search form. I can now see that I need to re-think portions of the
database GUI.

Thanks again,

John

May 5 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.