Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Data Binding issues
Message
De
28/02/2008 12:31:20
Timothy Bryan
Sharpline Consultants
Conroe, Texas, États-Unis
 
 
À
28/02/2008 09:59:39
Frank Dolinar
Mi House of Representatives
Michigan, États-Unis
Information générale
Forum:
ASP.NET
Catégorie:
The Mere Mortals .NET Framework
Versions des environnements
Environment:
VB 8.0
OS:
Windows XP SP2
Network:
Novell 6.x
Database:
MS SQL Server
Divers
Thread ID:
01297359
Message ID:
01297462
Vues:
16
This message has been marked as the solution to the initial question of the thread.
>We're having trouble with data binding various MM.Net controls. The problems we're finding seem to be intermittent, or at least not consistent. We're relatively new with MM.Net, so it's possible that we're missing something fundamental. Regardless, we apparently need some help.
>
>Here's the problem.
>
>We can select a control and specify a binding source from the properties window.
>Attempts to set a BindingSourceMember, BindingSourceDisplayMember, or BindingSourceValueMember displays an error dialog which presents the following text:
>----------
>Error message: Cannot bind to the new display member
>Parameter name: newDisplayMember
>----------
>These lines are followed by 7 more lines describing the call stack.
>
>We encountered this at first with a listbox, which we expected to work like grids, based on the Jump Start tutorials, and grids appear to function as advertised. We did eventually manage a workaround for the listbox issue, supported by content in the MM.Net documentation, and thought that was the end of the problem.
>
>We instantiate local objects and register them with the form(s) in question and have gone through all the setup delineated in the JumpStart tutorials (at least we believe we have).
>
>Then, yesterday, we encountered the same frustrating problem with a textbox on one of our forms.
>
>We're disappointed, to say the least, that the data binding doesn't work. Our first thought was that we have missed something, again. And that may be true, but a couple of days of diligent searching through the documentation and doing internet searches have not provided an answer.
>
>I'm assuming that if we see a list of business object which may be used as a BindingSource and select one for the particular control that the fields / columns identified by that business object's entity file should all be available when I need to specify a BindingSourceMember.
>
>Is there some setting or handful of code that needs to be set up for this to work.
>Any help will be much appreciated.


Frank, I have experienced this when trying to use the builder/ picker to pick the BindingSourceMember. I think it might depend on the database you are using, but when I just type in the value for BindingSourceMember in the property sheet it has always worked for me.
Tim
Timothy Bryan
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform