Dependency problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Fellow programmers, this is a weird one. I have had this happen a couple of
times before, but don't remember what I did to solve the problem.

I have form fields referenced in the source of dropdown fields (like
[Forms]![frmWhatever]![cboWhatever].

I also use an existing form and use the Save As to save it as a new form if
the existing form is similar to the new form I want to create.

Nothing out of the ordinary.

Once in a while, there is a dependency problem where a form ends up
dependent on another form where there really shouldn't be a dependency.

This is a direct result of using the Save As and having the form ref in the
Criteria of one of my query fields. The form part of the ref reverts to
another form name.

It is normal and works, and then all of a sudden the ref in my query
changes. When I check the dependencies, I see that there is a dependency
between the 2 forms, but there shouldn't be.

I cannot figure out how to remove dependencies, if you even can do this, so
I am driving myself crazy trying to figure out how to solve this issue.

Just to be sure you unserstand, this is what I do:

1. Right-click on an existing form and choose Save As.
2. I enter my new form name.
3. I change things around as I see fit.
4. I have a dropdown or list box field on my form.
5. I set the source for this field and use a form ref as the criteria for
one of my query fields.
6. One day this weird dependency pops up that shouldn't exist.
7. The form ref as the crteria for one of my query fields for my dropdown or
listbox reverts to the form name that exists in the bogus dependency.
8. I change it back and it reverts again.

I would like to know why this happens and how to not have this happen, but I
also need to know a way to solve this everytime it happens.

To redo my form from scratch can take a lot of time, and I cannot make a new
form and copy the old form dropdown or list box, as this carries over the
bogus dependency. The only thing I know to do is to redo the forms.

Has anyone else seen this? Does anyone know what I can do to solve this?

Thanks,
Clint
 
cherman said:
Fellow programmers, this is a weird one. I have had this happen a couple of
times before, but don't remember what I did to solve the problem.

I have form fields referenced in the source of dropdown fields (like
[Forms]![frmWhatever]![cboWhatever].

I also use an existing form and use the Save As to save it as a new form if
the existing form is similar to the new form I want to create.

Nothing out of the ordinary.

Once in a while, there is a dependency problem where a form ends up
dependent on another form where there really shouldn't be a dependency.

This is a direct result of using the Save As and having the form ref in the
Criteria of one of my query fields. The form part of the ref reverts to
another form name.

It is normal and works, and then all of a sudden the ref in my query
changes. When I check the dependencies, I see that there is a dependency
between the 2 forms, but there shouldn't be.

I cannot figure out how to remove dependencies, if you even can do this, so
I am driving myself crazy trying to figure out how to solve this issue.

Just to be sure you unserstand, this is what I do:

1. Right-click on an existing form and choose Save As.
2. I enter my new form name.
3. I change things around as I see fit.
4. I have a dropdown or list box field on my form.
5. I set the source for this field and use a form ref as the criteria for
one of my query fields.
6. One day this weird dependency pops up that shouldn't exist.
7. The form ref as the crteria for one of my query fields for my dropdown or
listbox reverts to the form name that exists in the bogus dependency.
8. I change it back and it reverts again.

I would like to know why this happens and how to not have this happen, but I
also need to know a way to solve this everytime it happens.

To redo my form from scratch can take a lot of time, and I cannot make a new
form and copy the old form dropdown or list box, as this carries over the
bogus dependency. The only thing I know to do is to redo the forms.

Has anyone else seen this? Does anyone know what I can do to solve this?
Click to expand...


The first thing to do is turn OFF the Name AutoCorrect
option (Tools - Options menu)

See what effect that has on the problem and if it continues,
post back with what is happening after the option is turned
off.
 
That seems to have solved the problem. I remember reading that the
AutoCorrect feature can cause problems.

It's too bad because I like the feature and will have to remember that it is
off. Not that I need it all the time.

Thanks for your reply!!

Clint

Marshall Barton said:
cherman said:
Fellow programmers, this is a weird one. I have had this happen a couple of
times before, but don't remember what I did to solve the problem.

I have form fields referenced in the source of dropdown fields (like
[Forms]![frmWhatever]![cboWhatever].

I also use an existing form and use the Save As to save it as a new form if
the existing form is similar to the new form I want to create.

Nothing out of the ordinary.

Once in a while, there is a dependency problem where a form ends up
dependent on another form where there really shouldn't be a dependency.

This is a direct result of using the Save As and having the form ref in the
Criteria of one of my query fields. The form part of the ref reverts to
another form name.

It is normal and works, and then all of a sudden the ref in my query
changes. When I check the dependencies, I see that there is a dependency
between the 2 forms, but there shouldn't be.

I cannot figure out how to remove dependencies, if you even can do this, so
I am driving myself crazy trying to figure out how to solve this issue.

Just to be sure you unserstand, this is what I do:

1. Right-click on an existing form and choose Save As.
2. I enter my new form name.
3. I change things around as I see fit.
4. I have a dropdown or list box field on my form.
5. I set the source for this field and use a form ref as the criteria for
one of my query fields.
6. One day this weird dependency pops up that shouldn't exist.
7. The form ref as the crteria for one of my query fields for my dropdown or
listbox reverts to the form name that exists in the bogus dependency.
8. I change it back and it reverts again.

I would like to know why this happens and how to not have this happen, but I
also need to know a way to solve this everytime it happens.

To redo my form from scratch can take a lot of time, and I cannot make a new
form and copy the old form dropdown or list box, as this carries over the
bogus dependency. The only thing I know to do is to redo the forms.

Has anyone else seen this? Does anyone know what I can do to solve this?
Click to expand...


The first thing to do is turn OFF the Name AutoCorrect
option (Tools - Options menu)

See what effect that has on the problem and if it continues,
post back with what is happening after the option is turned
off.
Click to expand...
 
Back
Top