Re: form detailview question
- From: "GS" <gsmsnews.microsoft.comGS@xxxxxxxxxxxxxxxxx>
- Date: Sun, 16 Dec 2007 20:45:30 -0700
then it is the users wish to go against company policy to make meaningful
name. and he is going to suffer from the potential gain of meaning.
autogenerated key has no meaning neither. for alpha key in large table,
wide scatter of key values help performance but I double if small number of
similar key name make much difference in small tables of 100 entries or
less.
Furthermore, as long as the entry is not referenced, user will be allowed to
rename, change, delete. Once the entry is referenced , no change is allowed.
except for the admin person.
"Bob Powell [MVP]" <bob@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D0A0C151-64BE-4B8C-B034-36037F7AA9A6@xxxxxxxxxxxxxxxx
I think that even with advanced users, the primary key is best left tosome
automated process. User entered data tends to be subject to abuse, liketrying
someone calling all their entries "fred" or such.
--
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"GS" <gsmsnews.microsoft.comGS@xxxxxxxxxxxxxxxxx> wrote in message
news:OTX$hzuPIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Ordinarily, no.
this form deals with only a small number of named entries possibly less
than
50.
the name field is only 16 characters.
and the users using this form is either developer or advanced users
oftento customize the application data extraction pattern.
I suppose I could generate primary key and have unique index on name
field.. however in the application the references are by name not by
other
key for ease of use and maintenance by user.
"Bob Powell [MVP]" <bob@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3ABEDF9C-F6E0-4AF6-B140-AAF217390DEE@xxxxxxxxxxxxxxxx
Are you sure that allowing the user to fill the primary key is a goodidea?
These are often left to the database and the insert statement will
convention,accept all fields _except_ the primary key which is often, by
butautogenerated.binding
--
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"GS" <gsmsnews.microsoft.comGS@xxxxxxxxxxxxxxxxx> wrote in message
news:eRPPE2oPIHA.3556@xxxxxxxxxxxxxxxxxxxxxxx
in Windows form, I have Datagridview and detailview with the same
fielddata manager. upon clicking the + in the navigator, the primary key
is
blank as expected, but I need to enable it for new record to let user
to
fill it. On the other hand I don't want to allow change to the field
for
existing record. so disable that on existing non new record. How do I
do
that?
I notice the property of the fields are enabled in the form design,
could not find any code for disable them.
.
- References:
- form detailview question
- From: GS
- Re: form detailview question
- From: Bob Powell [MVP]
- Re: form detailview question
- From: GS
- Re: form detailview question
- From: Bob Powell [MVP]
- form detailview question
- Prev by Date: Re: make the computer press keys
- Next by Date: Re: make the computer press keys
- Previous by thread: Re: form detailview question
- Next by thread: Update UI from Background thread
- Index(es):
Relevant Pages
|
