This is an Access forms newsgroup, Ed. The Windows Forms used in .NET
Windows applications are a very different animal to Access forms. You need
to ask your .NET Windows Forms questions in a more appropriate newsgroup.
Try microsoft.public.dotnet.framework.windowsforms.databinding
BTW: The post you quoted sounds to me like it was not talking about a .NET
Windows Form at all. The terms 'Row Source' and 'Recordset' are not used in
.NET. In .NET you bind forms and controls using the Data Source and Data
Member properties, and you bind to datasets, data tables, arrays or
collections, not recordsets, not unless you're using COM Interop with legacy
'classic' ADO components.
My sincere apologies for hitting the wrong button for the forum of interest.
I intended to post this to the .net forms newsgroup, and yes I may be mixing
up the terminology, between 'legacy ADO, Ado.net, DAO, Classic Data Design,
E-R Design, Object Oriented Design, etc. Some of us have suffered through
all the various versions, consistencies, inconsistencies, similararites,
dis-similararties, and just plain muddling of terms between all of these.
As a result, our brains don't fire exactly right all the time.
Not to mention the various versions of "standard SQL" ;>
Please accept my humble apologies.
Ed Warren.
> This is an Access forms newsgroup, Ed. The Windows Forms used in .NET
> Windows applications are a very different animal to Access forms. You need
[quoted text clipped - 56 lines]
>>
>> Ed Warren.
Brendan Reynolds - 10 Jul 2005 15:47 GMT
No apologies necessary, Ed - just hoping to point you toward the most
relevant resources.

Signature
Brendan Reynolds (MVP)
> My sincere apologies for hitting the wrong button for the forum of
> interest. I intended to post this to the .net forms newsgroup, and yes I
[quoted text clipped - 71 lines]
>>>
>>> Ed Warren.