Hi all,

After spending about 6 months part-time experimenting with the 2005 pro vb.net interface using wizards, its my opinion that wizards should NOT be used to develop anything but fixed database prototypes.

I had actually started using code in 2005 but it was crashing so much that I tried the wizards.
The wizards didn't crash so much when building solutions.  I thought I had finally found a code generator that actually worked.  Come to find out only up to a point.

Once I started using the wizard, I had so many work arounds and crashes from attempting to change a database field that I finally gave up.  Some of the crashes were so bad they actually corrupted files.

The wizards are there just to "wow" unsuspecting parties into thinking its super easy to use.
Its not.  Its super easy to use exactly how they demo in the limited way of the drag-n-drop features and thats all.

Absolutly no support or demos regarding how to modify once built.
I tried chasing down the code behind the wizards but like every other code generator its so complex its propriatary and very easy to break.

Don't use the wizards as a coder.  Develop everything in code.

I could suggest only to use the wizards on a fixed database and never try to modify the db or the code.
Just re-wizards everything.

Or use the wizards to dupe unsuspecting clients into thinking its easy to use.

So please, please don't waste your time using the wizards.

---------------

James Crowley wrote:

This was still aimed with code-behind in mind. However, I've found a large number of people happily dragging and dropping components from the toolbox, or using the Microsoft wizards, with no real idea as to what each object actually *does*. Although the wizards are great time savers for many things, personally I still prefer writing my own logic for making calls to database stored procedures etc. But maybe I'm a control freak! In terms of layer segregation - there's no hint of layout code here. At the most, we're setting the DataSource for a datagrid - and then presumably the .aspx page would be dealing with the layout/appearance.

hey pls need help wit the connection string for using sql server wit ado.net. im not gettin the code lines for the connection .please help.its urgent

Hi Folks,

I keep getting this error when trying to connect to my sql dbase.

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I'm currently learning to use vb.net and sql server, so i am a novice. Any help would be gratefully appreciated.

kindest regards.

Hi, finally getting somewhere with my understanding of ADO but am still a bit lost with my predicament.

I have an Empress (SQL) database on a Linux server that I want to link to an MS Access database on a Win2000 PC (they are both on the same closed network).

Although I have read and understood the topic and have tried and failed to get my link to work I have somehow managed to get myself stuck in a neverending loop of confusion. I think I'm trying to do too many things with too many programming languages at the minute and am one stage away from placing my underpants on my head with a pencil up each nostril and need someone to guide me through to the next stage before I implode!

Thanks

Excellant article, very meaty and precise!

Here is a little utility for helping get the precise sequence of objects correct for a particular combination of request/data type, at least for SqlClient

http://www.nicecleanexample.com/Tools/SqlBuilder/SqlClient.aspx

jk