Replies

Thanks Hans (and Bryan)!

What a great way to deal with the issue. I created a table with a single entry for the FSC (ComboBox-list values). I then created a form (Additions/Deletes – False) for the manager to have an easy means of entry (Combo prevents keyboard errors [i.e. 1 vrs. .01 as percent] which is accessed from the switchboard. The OnLoad code works perfectly! I also set the form on the swithboard (Manager Options) to be viewable to the admin privileges only.

This is a great (and clean) way to resolve the problem. Thanks, once again, for making me out to be the hero!

Bryan

Thanks so much for you input Bryan (see next post)

Bryan

Thanks Hans! I like that line of logic. As I have to be in a meeting in ten minutes, I’ll give this a try this evening and post back with my attempts. Very much appreciate your input as always!

Bryan

That sounds reasonable. Will give it a try this evening and post back

Thanks!

Thanks for your reply Bryan!

I am using a CDRW and the file remains in read-only even if I uncheck the box.

Thanks Howard, but there are no “reports” run from this form.

I did manage to put the default as =Date() so the form would display at least something.

<>
I didn’t put that very well. What I meant to say was that it appears that you can’t simply refer to [Forms]![frmLoadBoardDateParameter]![StartDate] without having provided some way for the form to know that it needs to run the filter. Even when the date parameter is entered on the form, it doesn’t have “permission” to run the filter until the CmdApply is clicked. What I had been trying to do with a custom dialog form wasn’t working because Access was treating the criteria entry as parameter text. That’s why I kept getting the criteria in the default dialog. I guess.

Thanks Pat, I think our posts just passed each other.

I think I came up with an idea that follows your logic, but without utilizing the custom dialog.

Thanks!

Finally, an answer. Not the one they asked for, but one they like even better.

I abandoned the thought of using a custom dialog form for the input. One, because I wasn’t getting anywhere; and two, because in the middle of all this they wanted the parameters to be displayed on the open form. (apparently people loose track of what dates they have entered).

I now have two text boxes in the form header for start and end dates, with a Cmd button to apply the dates. The on click event runs a macro (apply filter) which runs the query with the parameters designated on the form. Works great and everyone is happy – the date parameters are even shown in the header.

I suppose (guess) that the criteria option in the select query only permits input from the source of the query. In using unbound text boxes on the form, and then the command button to run the query, a frm filter is created with the date parameter. This only works after the form has been opened, so I had to change the form source to the table the qry is based on rather the the qry itself.

Thanks for your input!!

OK. I can’t even see the trees now.

You don’t mean to put a Command Button on the query do you? How do you do that?
The frmLoadBoardDateParameter is based on the qfltLoadBoardDateParameter and doesn’t even open until the query parameters are entered.

I tried to look at this a little differently by placing a command button on the form and using the on click event to call mcrqfltLoadBoardDateParameter, but still get the same default Access parameter window. Still no custom form.

No cigar.

I created a new unbound form (frmEnterDates) with two text boxes (StartDate and EndDate) with the input masks for short date. I went back to the qry and entered the following in the criteria:

Between [Forms]![frmEnterDates]![StartDate] And [Forms]![frmEnterDates]![EndDate]

I’m still getting the default Access parameter window with the text “[Forms]![frmEnterDates]![StartDate]” displayed. If you make an entry here (still no input mask) it takes you to the next Access default parameter window with the text “[Forms]![frmEnterDates]![EndDate]” displayed. It is not opening the custom form.

Thanks for the input Hans. I gave this some considerable effort, and then just scanned the docs into the existing forms as bound objects. Not as clean as I would have preferred, but the results seem to work OK.

Thank you for your time Hans. I don’t have a clue how to zip a db, so I guess I’ll have to deal with it at a later time. I have to leave the office for a meeting so I’ll try again tomorrow I guess. Boy, am I ever gonna be in trouble.

Thanks again

Thanks for responding Hans.

1) I did that.

2) The only event properties on the form (there are none for the actual form) are for combo boxes, and they are limited to OnNotInList and dblClick.

I just KNEW there had to be a way! Actually, I had given up after littering my office floor with every book on Access I own, and several pieces of wadded up scratch paper. I finally quit when I read that the “&” sign could not be used in a conditional statement (but that was a book on Access 97). So, either you’ve made a liar out of them or there is a difference between ’97 and 2000. At any rate, you have not only solved the immediate problem rather famously, but you have taught me a rather valuable lesson – don’t always believe what you read, and there are people at Woody’s who have far more talent than I might have patience.

This idea of using a naming “convention” (i.e. the “only” statement) in the table the combo box is built on, along with your generous Expression Is contribution, opens up a whole new way of thinking for me in other applications as well. I am, indeed, in your debt.

Thanks!