Design-time error - don't get it...

  • Thread starter Thread starter Tom Rahav
  • Start date Start date
T

Tom Rahav

Hi.
I develop VB.NET for about 2 year.... recently, I created some user
controls, and use them in a win-form. Sometimes, when I try to design a form
that contains these controls, I get error messages that I know as RUNTIME
errors, such as "Dynamic SQL generation is not supported against a
SelectCommand that does not return any base table information." ... I don't
get it! I try to design the form in design mode!! when I click OK on that
error message, I get an error page describes the error, instead of the
original control.
It happened to me few times, and there is nothing I can do to solve it or
continue working !
Can someone please help here?

Thanks!
Tom Rahav.
 
Tom Rahav said:
Hi.
I develop VB.NET for about 2 year.... recently, I created some user
controls, and use them in a win-form. Sometimes, when I try to design a
form that contains these controls, I get error messages that I know as
RUNTIME errors, such as "Dynamic SQL generation is not supported against a
SelectCommand that does not return any base table information." ... I
don't get it! I try to design the form in design mode!! when I click OK on
that error message, I get an error page describes the error, instead of
the original control.
It happened to me few times, and there is nothing I can do to solve it or
continue working !
Can someone please help here?

Thanks!
Tom Rahav.
While your project is in design mode, the control instances you are using
are in run mode. Think about it. If the controls were not in run mode, (and,
this goes for native control instances as well) how could you set properties
and have your settings reflected in the designer? It sounds to me like the
controls you are using are expecting to find certain other objects or
properties available, and are not finding what they need. I'd check the
documentation for these controls to see what requirements are listed.
 
Thanks for Peter's input.

Hi Tom,

From the error info you provided, it is something related to using the
database CommandBuilder to generate sqlstatement at design-time. So there
must exists some DataAdapter in your custom winform control ,yes?

Also, based on my research, there're some former issues whch has the
similiar symptom, most of them are caused by the different(Sql or OleDb
)CommandBuilder's support for different sqlstatement syntax. So does the
problem occurs when your control use a certain database's commandbuilder.
If convenient, I'd suggest you also provide some code snippet and the
select statement you're using when encounter the error.

If there is any other finding, please feel free to post here.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Tom,

In my opinion is for this error only one thing important, how does your
Select String looks like. The message says that for this Select String the
dynamic generation is not supported.

Just my idea.

Cor
 
Back
Top