I had a field in a table. The field is now gone, I got rid of it because it wasn't needed. This field itself was not in any relationships. It was just there. The table it was in does have a relationship,(If it matters, it was on the many end of a one to many) but I got rid of and re-wrote any querys and forms that it was in. So basically, this field DOES NOT exist. At all. When I try to open the table, I get a message: "Enter Parameter Value Modules.Company Name" . >:-< If I just enter nothing, the table comes up ok as far as I can tell. I cannot figure out why it thinks that field is still around. All I can think is there is some residual code lying around somewhere that you have to get rid of by hand, and I just don't know about it. I hope someone can help me Please!! [sig][/sig]
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
enter parameter value
- Thread starter katiekat
- Start date
MichaelRed
Programmer
KatieKat,
There are a multitude of potential hidden occurances of the 'obsolete' hidden field name references.
The CLUE here is the "Enter Parameter Value Modules.Company Name. and the use of the "Parameter Value" phrase.
The "Parameter" implies that the reference comes from a query -- as in "Parameter query". You need to check those "re-Written" queries to see if/which have the (not quite) obsolete field name as a parameter.
An alternative could be the use of the field as part of an expression in a validation rule(or text) for the table itself, or as part of a Lookup for a field in the table. Note that to find these nasty little "bugs" you need to look in both the General and LookUp field properties for each field in the table (in design view).
[sig]<p>MichaelRed<br><a href=mailto:mred@duvallgroup.com>mred@duvallgroup.com</a><br>There is never time to do it right but there is always time to do it over[/sig]
There are a multitude of potential hidden occurances of the 'obsolete' hidden field name references.
The CLUE here is the "Enter Parameter Value Modules.Company Name. and the use of the "Parameter Value" phrase.
The "Parameter" implies that the reference comes from a query -- as in "Parameter query". You need to check those "re-Written" queries to see if/which have the (not quite) obsolete field name as a parameter.
An alternative could be the use of the field as part of an expression in a validation rule(or text) for the table itself, or as part of a Lookup for a field in the table. Note that to find these nasty little "bugs" you need to look in both the General and LookUp field properties for each field in the table (in design view).
[sig]<p>MichaelRed<br><a href=mailto:mred@duvallgroup.com>mred@duvallgroup.com</a><br>There is never time to do it right but there is always time to do it over[/sig]
- Thread starter
- #3
Ok, by "re-written" I mean, I deleted the old ones and made new ones from scratch, after I had gotten rid of the field. So I don't think that has anything to do with it.
Maybe this will sound dumb, but it doesn't exist any more. Why should I set it up as a validation rule? Also, how can I look at any properties if I have deleted the field?
[sig][/sig]
Maybe this will sound dumb, but it doesn't exist any more. Why should I set it up as a validation rule? Also, how can I look at any properties if I have deleted the field?
[sig][/sig]
MichaelRed
Programmer
I don't mean for you to "set it up", but that IT might already exist as part of some OTHER field's validation rule or lookup. [sig]<p>MichaelRed<br><a href=mailto:mred@duvallgroup.com>mred@duvallgroup.com</a><br>There is never time to do it right but there is always time to do it over[/sig]
- Thread starter
- #5
I am trying to understand you here, but I obviously have no idea what you are talking about. The field itself was not attached to any other table in any way, nor was it attached to any other field in any way. It just sat there. It had no meaning, it was just plain old information that had to get recorded. It was actually a superfluous field, repeated in several tables because when I started, I thought I had to. I realized that I didn't, and got rid of all the stupid ones that I didn't need. I guess the thing is, I wouldn't know how to make some field part of some other field's validation rule or lookup, so I don't think that is an issue, unless that is somehow done automatically.
That field is not in any query. I know that. I looked at the code for it, and there is no [modules].[companyname] It doesn't exist. I know enough to be able to find that. [sig][/sig]
That field is not in any query. I know that. I looked at the code for it, and there is no [modules].[companyname] It doesn't exist. I know enough to be able to find that. [sig][/sig]
MichaelRed
Programmer
KatieKat,
For the Validation rule/lookup issue, I was refering to the item(s) on the bottom of the table design view screen, where you enter items like "Format", "Default Value" ...
Sorry about the confusion. Obviously, the database does have some reference to "companyname". Ms. Access does NOT search tables and queries for text entered in the "search" window, however it can search all of the code, so a simple search for "companyname" only really rules out the code/modules. Since the request comes from opening the table itself, the prompt MUST be from something attached to the TABLE, which - as far as I know - can only be in the properties of the fields/indicies/validation rules/defaultvalue ... in the same table.
From what you say here, I do not know of any other soloutions. [sig]<p>MichaelRed<br><a href=mailto:mred@duvallgroup.com>mred@duvallgroup.com</a><br>There is never time to do it right but there is always time to do it over[/sig]
For the Validation rule/lookup issue, I was refering to the item(s) on the bottom of the table design view screen, where you enter items like "Format", "Default Value" ...
Sorry about the confusion. Obviously, the database does have some reference to "companyname". Ms. Access does NOT search tables and queries for text entered in the "search" window, however it can search all of the code, so a simple search for "companyname" only really rules out the code/modules. Since the request comes from opening the table itself, the prompt MUST be from something attached to the TABLE, which - as far as I know - can only be in the properties of the fields/indicies/validation rules/defaultvalue ... in the same table.
From what you say here, I do not know of any other soloutions. [sig]<p>MichaelRed<br><a href=mailto:mred@duvallgroup.com>mred@duvallgroup.com</a><br>There is never time to do it right but there is always time to do it over[/sig]
- Thread starter
- #7
WELL! You know what? This is how I "fixed" it. I copied and renamed the tables. I no longer get the error. Interesting huh? Why that fixed it, I have not a clue. It's lovely.
Also, you shouldn't assume people are stupid because they aren't programmers. [sig][/sig]
Also, you shouldn't assume people are stupid because they aren't programmers. [sig][/sig]
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
