"Enter Parameter Value" problem; me, too.

[StargateFanFromWork]

I've been trying to hunt down the culprit for over a week but must admit
defeat. With the help of various archive articles, have been trying to
figure why this "Enter Parameter Value" box now pops up each time we start
the front end.

The difficulty is that the autonumber field called "DocketID" is in
everything! It's in the tables, in the forms and in the queries,
everywhere. Somewhere along the way when I first started really getting
into A2K just a few short weeks ago, I did up a form I believe it was and
then I think that particular form was deleted. I'm not even 100% sure if it
was a form, but I believe that's what it was. After that, this box always
pops up. Does anyone have any hints on how to narrow down the culprit? I
have 2 1/2 weeks left in this contract and my front end has a lot of
customizations/queries and reports that my colleagues need. However, I'd
hate to give this copy around with this parameter box popping up at the
beginning all the time. It doesn't look good and is not necessary. Any
tips appreciated and thanks! D

 

[Ken Snell \(MVP\)]

Oftentimes, this parameter results from the presence of the "field name" in
the Sorting & Grouping property in a report that is being opened.

It also can be in the LinkMasterFields or LinkChildFields property of a
subform control in a form.

What are you doing when the paramater value window is displayed? or rather,
what did you do just before it is displayed?

 

[Van T. Dinh]

1. Start with the "Startup" Form if you assigned a Startup Form in the
Startup Options ... If you use AutoExec Macro, check the Macro actions for
processes run by the Macro.

You can try remove the Startup Form from the StartUp Options, close the
database then re-open the database. If the Enter Parameter dialog box
doesn't appear, you know the problem is in the Startup Form!

2. In the Startup Form (or a Form opened by AutoExec), check:

* The Query or SQL String being used as the RecordSource for the Form and
make sure ALL Field names are correct since unrecognised Field name(s) will
be treated as Parameters and hence the prompt.

Run the Query/SQL by itself, i.e. not through the Form and see if the dialog
comes up. If it doesn't, you know the problem is not in the RecordSource
Query / SQL String.

* The Filter Property and the OrderBy of the Form. If you have anything in
these 2 Properties, delete and try your Form.

* If the code in the Startup Form opens a another Form or a Report or a
Query, you need to check these also.

There are other causes depending on the set-up of the Startup Forms /
actions of your AutoExec Macro but the above causes are the most common ...

Post details of your check for the above if you need further help ...

 

[StargateFan]

1. Start with the "Startup" Form if you assigned a Startup Form in the
Startup Options ... If you use AutoExec Macro, check the Macro actions for
processes run by the Macro.

YES! I get this right at startup. This form opens almost right after
the parameter query box after we press okay. I asked for it to be
called right at the beginning as our network is very slow. Although
users no longer see the form once the startup routine is done as the
switchboard opens up over it, the forms "opens" up in an instant.

You can try remove the Startup Form from the StartUp Options, close the
database then re-open the database. If the Enter Parameter dialog box
doesn't appear, you know the problem is in the Startup Form!

Though I'm almost 100% sure it's got to be the form, I'll do this to
check.

2. In the Startup Form (or a Form opened by AutoExec), check:

* The Query or SQL String being used as the RecordSource for the Form and
make sure ALL Field names are correct since unrecognised Field name(s) will
be treated as Parameters and hence the prompt.

Run the Query/SQL by itself, i.e. not through the Form and see if the dialog
comes up. If it doesn't, you know the problem is not in the RecordSource
Query / SQL String.

* The Filter Property and the OrderBy of the Form. If you have anything in
these 2 Properties, delete and try your Form.

* If the code in the Startup Form opens a another Form or a Report or a
Query, you need to check these also.

There are other causes depending on the set-up of the Startup Forms /
actions of your AutoExec Macro but the above causes are the most common ...

Post details of your check for the above if you need further help ...

Thank you! Hopefully this great detail above will do the trick ...
<g>

 

[StargateFan]

Oftentimes, this parameter results from the presence of the "field name" in
the Sorting & Grouping property in a report that is being opened.

It also can be in the LinkMasterFields or LinkChildFields property of a
subform control in a form.

What are you doing when the paramater value window is displayed? or rather,
what did you do just before it is displayed?

Van T. Dinh covered the startup issues and it's right at the
beginning. I should have mentioned that, sorry. It's the form that's
called through code in the auto open routine. I'll check that later
on today when I get to the office. I'm hoping that it's something
there in that form after all. I've checked everywhere else, too.

Thanks! D

 

[StargateFanFromWork]

YES! I get this right at startup. This form opens almost right after
the parameter query box after we press okay. I asked for it to be
called right at the beginning as our network is very slow. Although
users no longer see the form once the startup routine is done as the
switchboard opens up over it, the forms "opens" up in an instant.

I'm such a bird-brain. I've already been through all this, I was just
forgetting all the things I've been through. So I'm breaking it down.

Though I'm almost 100% sure it's got to be the form, I'll do this to
check.

Did. Nothing changes.

Okay, here's where I'm always getting bogged down. In the recordsource for
this form, can you believe all that comes up?? I'd never copied it and then
pasted it in notepad, for example, so didn't realize all that was involved.
Here's what the recordsource for the form that comes up on startup says:

SELECT [Dockets].[DocketID], [Dockets].[OriginalDocketID],
[Dockets].[DocketSubject], [Dockets].[Status], [Dockets].[Category],
[Dockets].[Action], [Dockets].[Colour], [Dockets].[Section],
[Dockets].[Related Grey], [Dockets].[FileLocationID], [Dockets].[Other
import notes], [Dockets].[StartDate], [Dockets].[DueDate],
[Dockets].[CloseDate] FROM Dockets;

Looking at the above, I just don't see how I'm going to figure out where the
problem lies.

Going to keep trying, though.

Thanks.

 

[Ken Snell \(MVP\)]

From your original post, you said that the parameter being requested by
ACCESS is DocketID. See the first field in the recordsource's SQL statement?
It is the DocketID field in Dockets table.

If that field no longer exists in the Dockets table, then you need to delete
that field from this SQL statement.
--

Ken Snell
<MS ACCESS MVP>

Okay, here's where I'm always getting bogged down. In the recordsource
for
this form, can you believe all that comes up?? I'd never copied it and
then
pasted it in notepad, for example, so didn't realize all that was
involved.
Here's what the recordsource for the form that comes up on startup says:

SELECT [Dockets].[DocketID], [Dockets].[OriginalDocketID],
[Dockets].[DocketSubject], [Dockets].[Status], [Dockets].[Category],
[Dockets].[Action], [Dockets].[Colour], [Dockets].[Section],
[Dockets].[Related Grey], [Dockets].[FileLocationID], [Dockets].[Other
import notes], [Dockets].[StartDate], [Dockets].[DueDate],
[Dockets].[CloseDate] FROM Dockets;

Looking at the above, I just don't see how I'm going to figure out where
the
problem lies.

Going to keep trying, though.

Thanks.

Thank you! Hopefully this great detail above will do the trick ...
<g>

 

[StargateFanFromWork]

From your original post, you said that the parameter being requested by
ACCESS is DocketID. See the first field in the recordsource's SQL statement?
It is the DocketID field in Dockets table.

Ken, sorry for being so slow. I see it now. We're up to our eyeballs in
stuff as polling day is this coming Friday yet still have to fix this and
it's becoming a little confusing.

If that field no longer exists in the Dockets table, then you need to delete
that field from this SQL statement.

No, the DocketID field exists everywhere. That's the problem. It's in
practically every table/query/report there is as my supervisor used this
number for our dockets (I know, I know, we're told not use a primary key
autonumber field for a user number but there we are. There's nothing I can
do.).

To tell you the truth, I'm not any closer to finding where this is and I've
asked my colleague if she can live with this box coming up and she said yes.
So I think I'm going to shelve the problem for now. I've spent a long time
behind the scenes before posting this msg and since and I've tried my best
but this db is too big and I didn't create it so tough to figure out the
maze through all the reports/queries, etc. to figure out which DocketID
where is causing the problem. It might not even have been anything I did
but something my boss added later that coincidentally brought up the box.
We have 12 reports, 21 forms, 25 queries and 24 tables. I think I can be
forgiven for giving it my best shot but giving up at this point <g>. It's
best if I go on to battles I am more sure of winning esp. in the short time
I have left in this contract! <lol>

Thank you so much to everyone for their help with this. Appreciate it very
much, as always.

Cheers! D

--

Ken Snell
<MS ACCESS MVP>

Okay, here's where I'm always getting bogged down. In the recordsource
for
this form, can you believe all that comes up?? I'd never copied it and
then
pasted it in notepad, for example, so didn't realize all that was
involved.
Here's what the recordsource for the form that comes up on startup says:

SELECT [Dockets].[DocketID], [Dockets].[OriginalDocketID],
[Dockets].[DocketSubject], [Dockets].[Status], [Dockets].[Category],
[Dockets].[Action], [Dockets].[Colour], [Dockets].[Section],
[Dockets].[Related Grey], [Dockets].[FileLocationID], [Dockets].[Other
import notes], [Dockets].[StartDate], [Dockets].[DueDate],
[Dockets].[CloseDate] FROM Dockets;

Looking at the above, I just don't see how I'm going to figure out where
the
problem lies.

Going to keep trying, though.

Thanks.

Run the Query/SQL by itself, i.e. not through the Form and see if the dialog
comes up. If it doesn't, you know the problem is not in the
RecordSource
Query / SQL String.

* The Filter Property and the OrderBy of the Form. If you have

anything
in

these 2 Properties, delete and try your Form.

* If the code in the Startup Form opens a another Form or a Report or a
Query, you need to check these also.

There are other causes depending on the set-up of the Startup Forms /
actions of your AutoExec Macro but the above causes are the most

common
...

Post details of your check for the above if you need further help ...

Thank you! Hopefully this great detail above will do the trick ...
<g>

 

[Ken Snell \(MVP\)]

When you can break from the hectic preparations, feel free to post back. I'm
thinking that we're not completely understanding what you're seeing that you
don't want to see. You can post more details about the tables, etc. at that
time. Good luck.

 

[StargateFanFromWork]

When you can break from the hectic preparations, feel free to post back. I'm
thinking that we're not completely understanding what you're seeing that you
don't want to see. You can post more details about the tables, etc. at that
time. Good luck.

<g> Thanks! I finish here on Feb.03.2006 and had been hoping to try to
figure out why this dialogue box keeps popping up on the startup of the db.
It's one that says "Enter Parameter Value" on the title bar and then says
"DocketID" above the box the user would input something in. So every time
this db starts, I have to click OK on that box to make it go away. But it's
eluding me where this box is originating from. Even when the form isn't
opened on startup, this box _still_ comes up. That's what has been so
confusing. Only the db window and the switchboard open up when I remove the
form from the code in the switchboard on startup in the vbe so I'm at a loss
to know what is originating this request for a parameter value.

But as I mentioned, I'm only here for another 2 weeks as my contract is
ending (health issues have become pronounced so will not make it to the
original end of my contract). Anywho, my colleague says she can live with
this behaviour as my front end has things that the very basic one everyone
else has doesn't and it's a fair trade-off! <g>

Thank you! D

p.s., I just might be allowed to make a copy of both fe and be for my
personal use later and I might pursue this later on down the road when I
know more about A2K just to figure out where the problem lies for my own
curiousity.

 

[Ken Snell \(MVP\)]

Based on your description, it's either in an AutoExec macro's actions
(something that is being opened or run that contains a field named
DocketID), or it's something in the switchboard (perhaps a RowSource of a
combo box in that switchboard).

 

[StargateFan]

Based on your description, it's either in an AutoExec macro's actions
(something that is being opened or run that contains a field named
DocketID), or it's something in the switchboard (perhaps a RowSource of a
combo box in that switchboard).

I just had the same thing happen last night when I did up another
report for the team. I get two parameter value boxes when opening
this new one <lol>.

And I found out why this can be so prevalent in this db. To get the
results needed, my supervisor had to create queries based on sometimes
other queries! She's the one that's the pro, so I don't question that
but it makes my life interesting as I'm the one she's been turning to
to do some of the fine tuning <g>. So that's what has been making me
hopelessly muddled as I didn't know that before.

I now get 2 other of these parameter values boxes upon opening this
new report. So I'm on alert now. You can bet I'll be studying any db
I now come across to start learning what I'm dealing with re this type
of thing and I'll be paying closer attention to everything in the
properties. I'll get it yet even if not in time for this job.

I'll check _again_ <g>, though, re the switchboard but as I mentioned,
_all_ reports/queries/and forms have this field, every single last one
of them which is what is making this quite challenging.

Thanks!! Really appreciate the help. D

[snip]