Continuous Form Query

[louisa]

Hi everyone,

I have a form in my db called equipment, the form is set to a continuous for therefore all the text box's in the first row duplicate every time information is entered. This works very well for me. I have a field called MAC Address and this will only apply to the first item entered (it will not apply to anything else) so i am hoping for a way that that specific text box will be on the first row but for it not to duplicate.

Any way i can do this? Many thanks

 

[missinglinq]

...the form is set to a continuous for therefore all the text box's in the first row duplicate every time information is entered.

Sorry, louisa, but what your post lacks in clarity is only made up for by your obfuscation!

Are you saying that if you enter data in the MAC Address field of a record, this data appears in the MAC Address field of all visible records? If so, then the MAC Address field is not bound to a field in the form's underlying table/query. The solution to this set a field in the form's Recordsource as the Control Source for MAC Address.

If you're saying that you only want the textbox holding the MAC Address field to be visible in the first record but not in subsequent records, then the answer is No. In Continuous View and Datasheet View Forms either all records show a given control or they don't. In some cases you can use Conditional Formatting to display data or not, but I don't really see that being applicable here.

Linq ;0)>

 

[PNGBill]

I recently wanted a Command Button to be different (Conditional) on the records of a continuous form and was advised to use a text box control and conditional formatting.

If this could work for your text box control? Maybe have record numbering or some way for the events/condition to know which is the first record.

You should first ensure all else is normal and that there is not some fundamental error in the way you present your data.

Why can't the Mac Address Control be in the Form Header?

 

[vbaInet]

I think that's what she's after missinglinq.

So maybe conditional formatting using DMin() with a fore and back color of White could be the answer. Obviously some coding would need to be done in the After Update event of the textbox to test for DMin() AND Len(txtboxName & "") <> 0