G
GrahamK
I have created a form, every time I open it an "Enter Parameter Value" box
appears, how do I get rid of it?
appears, how do I get rid of it?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Allen Browne
GrahamK said:I have created a form, every time I open it an "Enter Parameter Value" box
appears, how do I get rid of it?
The request for a parameter means that Access is coming across a name that
it does not recognise.
For example, if the form is bound to a Client table that has a field named
LastName (without a space), but your form is requesting a field called Last
Name (with a space), Access will pop up a dialog asking for the Last Name.
The title of the parameter dialog shows you the name it can't find.
Once you know that, you will be looking for where that name is being
requested. Open the form in deisgn view, and look at its RecordSource
property. If this is a query (or a query statement), is the bad name in
there?
Also look in the RowSource property of any combo boxes or list boxes on the
form.
If the form has a subform, it could be in the subform's RecordSource or the
RowSource of its controls.
If none of that works, the problem name might be in the ControlSource of one
of the controls on the form.
Once you've found it, post a reply telling us where it was.
A
a a r o n _ k e m p f
move to SQL Server.. when you have problems like this you could just
run profiler to see what's really happening
run profiler to see what's really happening
T
Tony Toews [MVP]
GrahamK said:I have created a form, every time I open it an "Enter Parameter Value" box
appears, how do I get rid of it?
Note that Aaron Kempf's posting had absolutely nothing to do with your
problem.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
a a r o n _ k e m p f
bullshit a$$hole
if you used profiler; you could enter something.. and then see where
it is being used
maybe Tony should STFU and learn some enterprise level tools instead
of following me around.. _STALKING_ me and just saying 'no it isn't'.
Your worthless banter is more obnoxious that I have ever been.
YES. MY SOLUTION WOULD HELP THEM IMMENSELY.
-Aaron
if you used profiler; you could enter something.. and then see where
it is being used
maybe Tony should STFU and learn some enterprise level tools instead
of following me around.. _STALKING_ me and just saying 'no it isn't'.
Your worthless banter is more obnoxious that I have ever been.
YES. MY SOLUTION WOULD HELP THEM IMMENSELY.
-Aaron
L
Larry Linson
If Mr. Kempf were as knowledgeable about Access as he would like us to
believe, he would know that there are two third-party products (and both get
good reviews) with which you do exactly what he describes a profiler as
doing: you enter text, and they display to you every place in your Access
front end that the text string is used. If you have a problem determining
where in your _tables_ it is used, they can be run against the split
back-end, too.
The products are
(1) Rick Fisher's Find and Replace, shareware, available from
http://www.rickworld.com. I recently used it to identify a problem in a
colleague's client's database in less than two minutes that would otherwise
might have taken hours to locate.
(2) Speed Ferret, commercial software, from Black Moshannon Systems,
http://www.moshannon.com. Unfortunately, Speed Ferret was not updated for
Access 2003, so to use it you have to bring up an older version of Access
(2000 or 2002), with the accompanying delays. I am hoping they will soon
release an update for the most recent versions of Access.
Both of them allow you to, optionally, replace the found string with a
predetermined value.
As Mr. Kempf does not indicate what he would expect to be used as a front
end or user interface, nor the database engine he expects to be used as a
back end, nor what profiler he suggests, that is, his suggestion is generic
rather than specific. Thus, it is impossible to on the specifics of his
suggestion.
Larry Linson
Microsoft Office Access MVP
bullshit a$$hole
if you used profiler; you could enter something.. and then see where
it is being used
maybe Tony should STFU and learn some enterprise level tools instead
of following me around.. _STALKING_ me and just saying 'no it isn't'.
Your worthless banter is more obnoxious that I have ever been.
YES. MY SOLUTION WOULD HELP THEM IMMENSELY.
-Aaron
believe, he would know that there are two third-party products (and both get
good reviews) with which you do exactly what he describes a profiler as
doing: you enter text, and they display to you every place in your Access
front end that the text string is used. If you have a problem determining
where in your _tables_ it is used, they can be run against the split
back-end, too.
The products are
(1) Rick Fisher's Find and Replace, shareware, available from
http://www.rickworld.com. I recently used it to identify a problem in a
colleague's client's database in less than two minutes that would otherwise
might have taken hours to locate.
(2) Speed Ferret, commercial software, from Black Moshannon Systems,
http://www.moshannon.com. Unfortunately, Speed Ferret was not updated for
Access 2003, so to use it you have to bring up an older version of Access
(2000 or 2002), with the accompanying delays. I am hoping they will soon
release an update for the most recent versions of Access.
Both of them allow you to, optionally, replace the found string with a
predetermined value.
As Mr. Kempf does not indicate what he would expect to be used as a front
end or user interface, nor the database engine he expects to be used as a
back end, nor what profiler he suggests, that is, his suggestion is generic
rather than specific. Thus, it is impossible to on the specifics of his
suggestion.
Larry Linson
Microsoft Office Access MVP
bullshit a$$hole
if you used profiler; you could enter something.. and then see where
it is being used
maybe Tony should STFU and learn some enterprise level tools instead
of following me around.. _STALKING_ me and just saying 'no it isn't'.
Your worthless banter is more obnoxious that I have ever been.
YES. MY SOLUTION WOULD HELP THEM IMMENSELY.
-Aaron
A
a a r o n _ k e m p f
wow dude.
except.. you cannot search for query text (from dynamically built
queries)
with SQL Server-- or any grown up database-- it is easy to LOG the
queries you run so that you can thus determine what is going on in the
database TIER.
the point is that Access 'has no engine' and should not be considered
a modern relational database.
I would reccomend using Microsoft's reccomendation to upsize
everything to SQL Server (before you get stuck on the SharePoint
train)
except.. you cannot search for query text (from dynamically built
queries)
with SQL Server-- or any grown up database-- it is easy to LOG the
queries you run so that you can thus determine what is going on in the
database TIER.
the point is that Access 'has no engine' and should not be considered
a modern relational database.
I would reccomend using Microsoft's reccomendation to upsize
everything to SQL Server (before you get stuck on the SharePoint
train)
A
a a r o n _ k e m p f
re:
As Mr. Kempf does not indicate what he would expect to be used as a
front
end or user interface, nor the database engine he expects to be used
as a
back end, nor what profiler he suggests, that is, his suggestion is
generic
rather than specific. Thus, it is impossible to on the specifics of
his
suggestion.
As Mr. Kempf does not indicate what he would expect to be used as
a front
end or user interface,
(SQL Server and ADP)
nor the database engine
(SQL Server and ADP)
he expects to be used as a
back end, nor what profiler he suggests (SQL Server Profiler-- use
this thing called your EYES and read the post before needlessly
flaming people who are MUCH better programmers than you), that is, his
suggestion is generic
rather than specific. Thus, it is impossible to on the specifics of
his
suggestion.
(run SQL Server so that you can diagnose problems like this in the
future).
There are a billion reasons to run SQL Server-- from security to
administration to performance, extensibility, reporting and analytics.
being able to run profiler should be the 'bare minimum' available in a
relational database engine-- and thus anything that does not have this
capability is not 'business-ready'
As Mr. Kempf does not indicate what he would expect to be used as a
front
end or user interface, nor the database engine he expects to be used
as a
back end, nor what profiler he suggests, that is, his suggestion is
generic
rather than specific. Thus, it is impossible to on the specifics of
his
suggestion.
As Mr. Kempf does not indicate what he would expect to be used as
a front
end or user interface,
(SQL Server and ADP)
nor the database engine
(SQL Server and ADP)
he expects to be used as a
back end, nor what profiler he suggests (SQL Server Profiler-- use
this thing called your EYES and read the post before needlessly
flaming people who are MUCH better programmers than you), that is, his
suggestion is generic
rather than specific. Thus, it is impossible to on the specifics of
his
suggestion.
(run SQL Server so that you can diagnose problems like this in the
future).
There are a billion reasons to run SQL Server-- from security to
administration to performance, extensibility, reporting and analytics.
being able to run profiler should be the 'bare minimum' available in a
relational database engine-- and thus anything that does not have this
capability is not 'business-ready'