Solved

Prompted to save changes after applying a filter

Posted on 2004-09-14
10
315 Views
Last Modified: 2008-03-06
I have an Access Project connected to a SQL Server backend. There are a number of forms which are used to view the data and the "Filter by Form" button is used often to restrict the records displayed.

Whenever the users apply a filter and then close the form, they are asked whether they want to save their changes to the form. The only change they have made is to apply a temporary filter which they never want to save. In any case, the project is read-only so they cannot actually save the change anyway.

Is there any way to stop them being prompted if their only change is to apply a filter? I have tried intercepting the close event in order to undo the filter, but the prompt seems to come up before any of the events fire.
0
Comment
Question by:ChrisThornton
10 Comments
 
LVL 14

Expert Comment

by:bluelizard
ID: 12053105
my solution to this problem was a close button with the code

  DoCmd.Quit acQuitSaveNone

behind it (but make sure you don't use that button after actually modifying the database...)


--bluelizard
0
 
LVL 2

Author Comment

by:ChrisThornton
ID: 12053179
Unfortunately the users have been using this system for some time as an mde using DAO to connect to SQL Server, so they're pretty used to closing forms by using the little cross in the corner of the form or just closing the whole app. Incidentally, the mde incarnation of the system doesn't exhibit this behaviour (any idea why there's a difference?).
0
 
LVL 9

Expert Comment

by:solution46
ID: 12053481
mde files are locked and Access knows that the design of a form cannot be changed - there is probably a more accurate technical description out there but this is close enough.

Why not just make an mde of your new version?

s46.
0
 
LVL 2

Author Comment

by:ChrisThornton
ID: 12053568
I tried that, well an ADE which is the Access Project equivalent, but I still get the prompt. It is a little different though, in that it asks whether I want to save changes to the view which the form is based on rather than the form itself. Is the filter in the project trying to save as a "where" clause in the underlying object rather than as a normal Access filter?
0
 
LVL 2

Author Comment

by:ChrisThornton
ID: 12053770
Something else I just found:

It only prompts to save changes after using the "Filter by Form" button. Using "Filter by Selection" or the "Filter For" on the right-click pop-up menu doesn't cause the prompt on closing the form.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 41

Expert Comment

by:shanesuebsahakarn
ID: 12054272
I haven't tried this, but have you tried clearing the filter in the form's OnClose or Unload event?
0
 
LVL 2

Author Comment

by:ChrisThornton
ID: 12054394
That was my first thought too, but the prompt comes up before these events fire.
0
 
LVL 11

Accepted Solution

by:
miqrogroove earned 500 total points
ID: 12089562
ChrisThornton, this is actually a simple configuration problem.

Every Access form has a property called "Allow Design Changes".  It is hidden at the very bottom of the "Other" tab in the properties for the form.  The default value for this property is "All Views"  Regardless of whether the user actually has the ability to save the form, you must set this proptery to "Design View Only".  If you do not, then the tiniest little change to the form (even filters) will cause a save prompt.

Enjoy,
-- Miqro
0
 
LVL 2

Author Comment

by:ChrisThornton
ID: 12100528
Thanks Miqro.

I was really hoping it was going to be something simple - but it so seldom is.

Back to the Access for Beginners course for me!

Chris.
0
 
LVL 11

Expert Comment

by:miqrogroove
ID: 12103414
I think of Access as a million simple pieces put together.  It is often overwhealming, but reliably so.

Glad to help,
-- Miqro
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Most if not all databases provide tools to filter data; even simple mail-merge programs might offer basic filtering capabilities. This is so important that, although Access has many built-in features to help the user in this task, developers often n…
In Debugging – Part 1, you learned the basics of the debugging process. You learned how to avoid bugs, as well as how to utilize the Immediate window in the debugging process. This article takes things to the next level by showing you how you can us…
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now