VS Dataform Wizard doesn't gen correct code!

[Larry Woods]

Has anyone noticed that the VS Dataform wizard doesn't gen correctly
DISPLAYED results if you have an IDENTITY key defined for your table
(normal stuff, IMHO)? If your dataset is empty the first "Add" will display
TWO records on the resulting form. This is because they are creating a
'temporary' dataset with the changes; i.e., new record in this case, and
then they MERGE it into the existing dataset, which has a new row defined by
the 'currencymanager.AddNew' that was created when you pressed the Add
button (if you requested a single record format). In case you requested the
datagrid you get the bogus record displayed when you click 'Update.'

This behavior continues even after the first record; i.e., an additional
record is displayed. Of course, since the MERGE of the new record never
finds a record to merge into since it has a new IDENTITY defined for it,
which doesn't exist in the local dataset.

I've got to think that this has been pointed out to MS, or am I the only one
that has tried to use the wizard? (I like it for tables with LOTS of
fields. Saves time (?) )

Larry Woods

 

[Senthilkumar]

Hi Mr Larry,

I have seen the same behaviour with forms generated by the wizard. I almost
finished a project with the wizards, and then found out in a kind of master
detail form, when no child records exists for a master, you cant add a
child. This forced me to shelve the project and restart with a new base.

I dont know whether this has been reported to MS or not.

kesk

 

[Larry Woods]

EXACTLY my experience! I wasted about 3 weeks attempting to use their CRAP!
Now I'm looking at a complete rewrite.

As far as MS knowing... I'm guessing that this wizard is over 3 years old.
I can't believe that they DON'T know it.

(And then people question why more people aren't moving to .NET!)

Larry