I have a two subforms that are almost identicle, but a field that is one 
subform that is visble is set to no in the properties and still shows on the 
first sub form and not on the other subform.  I have found a solution to this 
from search (Thanks to Tom Wickerath) were you put the field into the header. 
 My question is why, even though the field is not visble would it still show 
in the subform on one subform but not another where the forms are almost 
identicle.  I have even tried copying the field from subform 2 (not 
displaying), deleting the field in subform 1 and pasting in the field from 
subform 2 (they both work off the same query).  

I am using this field in VB to pull a path for shell program so I do not 
want that path displayed to the end user.  I read a suggestion to delete the 
field on the subform and you can still use the info like it existed.  I tried 
this and VB does not recognize the data for the field if the field is not 
placed on the subform.  I have also tried to set the visablity to false on 
open (again this did not work).

Again, I found a solution to this, but I would like to know why.  Is it just 
a quirk or is there something I am overlooking? 

thanks,
Robert

I expect your subform is datasheet view. The visible property works on 
controls, not the datasheet view. You would need to set the column's hidden 
attribute (I think).

-- 
Duane Hookom
Microsoft Access MVP


"Robert_DubYa" wrote:

> I have a two subforms that are almost identicle, but a field that is one 
> subform that is visble is set to no in the properties and still shows on the 
> first sub form and not on the other subform.  I have found a solution to this 
> from search (Thanks to Tom Wickerath) were you put the field into the header. 
>  My question is why, even though the field is not visble would it still show 
> in the subform on one subform but not another where the forms are almost 
> identicle.  I have even tried copying the field from subform 2 (not 
> displaying), deleting the field in subform 1 and pasting in the field from 
> subform 2 (they both work off the same query).  
> 
> I am using this field in VB to pull a path for shell program so I do not 
> want that path displayed to the end user.  I read a suggestion to delete the 
> field on the subform and you can still use the info like it existed.  I tried 
> this and VB does not recognize the data for the field if the field is not 
> placed on the subform.  I have also tried to set the visablity to false on 
> open (again this did not work).
> 
> Again, I found a solution to this, but I would like to know why.  Is it just 
> a quirk or is there something I am overlooking? 
> 
> thanks,
> Robert