Saving One Access object with many open

[Len]

I often have several Access queries, tables, reports, etc. open
simultaneously. When working on one of these objects and attempting to save
my work, I sometimes get a dialogue box showing a list of all open objects.
My choices are to a) save all objects, b) click and unhighlight all the ones
I don't want to save and then save the single object or c) Cancel. I have
looked in Tools/Options for a switch to turn this feature off but to no
avail. I have also scrutinized both off-line and on-line help for a
solutiion. Is there a way to turn this feature off so that I can click the
'Save' icon to save just the one object?

PS This same question is posted in another location that doesn't seem to
get the attention this 'General Questions' section gets.

Thanks,

 

[PatHartman]

I have never found a solution for this either. On the other hand, Access is
just unstable enough so that you don't want to leave changed objects unsaved
for long.

 

[Larry Daugherty]

The best way to make those messages go away is to go back to basics
and design your application and its User Interface correctly. You
didn't once mention a *Form*. Forms are the primary means of
interacting with data in Access applications. If you and your users
are mucking around in the tables and interacting with multiple live
queries instead of using forms then you'll forever experience data
errors and write conflict notifications. As it is, you might as well
be using Excel and MS Query to do what you're doing. You aren't
taking advantage of the power available to you in Access.

People didn't answer your post because they knew that you wouldn't
like the answer.

If posting into multiple newsgroups then multipost: put the name of
every newsgroup in the list of newsgroups in the header of your
message. That way, an answer anywhere will appear everywhere. That
saves excessively wasting the time and effort of the unpaid
volunteers. You probably won't get answers if you put more than three
or so newsgroups in the list.

You might find it useful to visit www.mvps.org/access and browse the
site. Especially look for "netiquette" for guidance on using the
newsgroups.

HTH

 

[Len]

Larry,

I guess I didn't describe my problem very well. It has to do with Access
functionality, not Form functionality. Maybe you're responding to someone
else's problem? I'm not sure what messages you are referrring to. I don't
know what you mean by 'you and your users mucking around'. I didn't mention
any users. I didn't mention write conflict notifications. I didn't complain
about not getting answers. And I'm not posting to multiple newsgroups.

And finally, your suggestion that I look up 'netiquette' implies that I said
something offensive or improper when nothing in my post could be remotely
construed as improper. The more I read your response, the more I'm convinced
that you are writing to someone else and posted to my question by mistake.

Len
--
"All those who suffer in the world do so because of a desire for their own
happiness. All those happy in the world are so because of their desire for
the happiness of others." --Shantidiva

The best way to make those messages go away is to go back to basics
and design your application and its User Interface correctly. You
didn't once mention a *Form*. Forms are the primary means of
interacting with data in Access applications. If you and your users
are mucking around in the tables and interacting with multiple live
queries instead of using forms then you'll forever experience data
errors and write conflict notifications. As it is, you might as well
be using Excel and MS Query to do what you're doing. You aren't
taking advantage of the power available to you in Access.

People didn't answer your post because they knew that you wouldn't
like the answer.

If posting into multiple newsgroups then multipost: put the name of
every newsgroup in the list of newsgroups in the header of your
message. That way, an answer anywhere will appear everywhere. That
saves excessively wasting the time and effort of the unpaid
volunteers. You probably won't get answers if you put more than three
or so newsgroups in the list.

You might find it useful to visit www.mvps.org/access and browse the
site. Especially look for "netiquette" for guidance on using the
newsgroups.

HTH

 

[Larry Daugherty]

Nope, I was responding to your post. I believe I understood your post
and problem fairly well and that everything in my earlier response is
appropriate.

My response wasn't an attempt to provide you with an answer to your
request. The problems you experience are due to your practices, not
Access functionality nor Form functionality. As I implied in my
response, you don't seem to be massaging your data from a well
designed application using Forms. You are getting at and possibly
modifying the same data via more than one path and it sounds like you
are the only one using your system!

It's your business how you use the resources at your disposal.
However, the volunteers responding in these newsgroups are doing so to
help Access developers at all levels with their current burning
*development* issues. Sometimes it takes the form of providing
concepts and general guidance. Sometimes it takes the form of
explicit code procedures. Often it is a matter of pointing out other
relevant resources.

By the way, yours was a valid question. How would you know if you
didn't ask? I believe that my response is a much better answer for
you than the one you actually sought.

No, you didn't mention users but, every application has users. In
your case it seems to be just one. I have the impression that you've
done your user a disservice by not providing a very useful or
trustworthy application.

We're not the Access Cops. We try to help developers solve problems.
We're also not Net Nazis. You mentioned:

The information about posting and things you might find on

www.mvps.org/access

were not to imply that you've done anything wrong but to refer you to
a resource that might help you to do a lot of things right.

There are quite a few Access related newsgroups. A couple that are
especially useful to novices are:

microsoft.public.access.gettingstarted and
microsoft.public.access.tablesdesign

HTH
--
-Larry-
--

Larry,

I guess I didn't describe my problem very well. It has to do with Access
functionality, not Form functionality. Maybe you're responding to someone
else's problem? I'm not sure what messages you are referrring to. I don't
know what you mean by 'you and your users mucking around'. I didn't mention
any users. I didn't mention write conflict notifications. I didn't complain
about not getting answers. And I'm not posting to multiple newsgroups.

And finally, your suggestion that I look up 'netiquette' implies that I said
something offensive or improper when nothing in my post could be remotely
construed as improper. The more I read your response, the more I'm convinced
that you are writing to someone else and posted to my question by mistake.

Len