columbos14927 wrote: but the CustomerId is changed from 3045 to 1 and save I am going to guess that CustomerID at the database level is an Identity Column? If that's the case then the value you are trying to set is not going to be accepted by the database engine. Common sense is admitting there is cause and effect and that you can exert some control over what you understand.

can you post the code for Mouse down

You can always consider using the Infragistics persistance framework to save and retrieve control state - http://www.infragistics.com/products/silverlight/persistence-framework/[^]. Or its not too difficult building your own framework - just serialize and store control attributes directly in the database. Apps - Color Analyzer | Arctic | XKCD | Sound Meter | Speed Dial

You *always* have a View, VM and Model. None of the parts are optional. View - Strictly 100% XAML (in fact, I prefer to delete the code behind entirely to prevent lazy programmers from uglifying the code). Some people will argue this is not a requirement, but IMO, it should be, it keeps the code cleaner. If you need to do something "complex" with a control, it shouldn't be done in the code behind, but rather broken out into a reusable UserControl. ViewModel - View binds to this class. Someone will now argue: but how do I set the VM since you have deleted the code behind? -- Answer: ViewLocator & DI. DI plays a second part in this class. It is used to inject the model into the constructor. ViewModel just wraps the Model with lazy load style properties and exposes commands that operate on the model, etc. Model - This is the API / storage layer of your objects. I like to break this out into its own assembly that a single programmer is managing for consistency. This is the *only* assembly that should even know what a database is. No database / persistence code of any kind is allowed anywhere else in the project. I like breaking the model out into its own assembly to keep things clean and in one place. Model should implement INPC and INCC.

Thanks!!!

columbos14927 wrote: the automaticly generated columns are not in the order that i would like them to be The turn off the auto generation and create the columns as you want them. Never underestimate the power of human stupidity RAH

Make sure you are accessing the UI / properties on the right thread. WP Apps - Color Search | Arctic | XKCD | Sound Meter | Speed Dial

Thanks!!!

Hey, No it doesn't work. The problem is when i switch to another tab and the come back the red Ellipsis disappear. Thanks.

columbos14927 wrote: 1.Validating user data a) client side input validation should be in presentation layer. b) Server side input validation should also be in presentation layer. c) Business rule validations should be in business logic layer. columbos14927 wrote: 2.Saving customer,staff member,vendor in to the DB. Actual data base CRUD operations will be in Data access layer but on successful validation the operation should be done in Business logic layer. columbos14927 wrote: 3.Retrieving customer,staff member,vendor from the DB. 4.Perform other DB related manipulation with customer,staff member,vendor. Again, the db layer should contain the data access logic and db entities. The actions should be triggered from business logic layer. Perhaps these article could be a little useful for you: Creating ASP.NET Applications with N-Tier Architecture[^] YaBlogEngine - A Tiny Blog Engine written in ASP.NET/C#[^] Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore, Dream. Discover.

Quite right. I'm usually pushing normalization myself. "The ones who care enough to do it right care too much to compromise." Matthew Faithfull

I used a wrap panel from the tool kit for this, bind it to a collection and add/delete the items in the collection. Never underestimate the power of human stupidity RAH

You don't appear to be setting the DataContext[^] anywhere. In the constructor, after you've created the list, try adding: DataContext = this; "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

The WPF toolkit on codeplex has a very good auto complete text box. Just google it as I haven't figured out how to copy paste on my tablet yet, sorry. When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman

What you basically need is a Mediator[^] that can act as a go between. Reading Sacha's article in the link I provided will be a good start. Good Luck! When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman

See WPF: A Beginner's Guide - Part 1 of n[^] for guidance on layout of controls.

hai am also getting same error have you found any solution..?:confused:

A WatermarkTextBox in 3 lines of XAML[^] should pretty much solve your problem. WP Apps - Color Search | Arctic | XKCD | Sound Meter | Speed Dial

Just do a search in the articles section on this site. There are a number of good samples and articles here. WP7.5 Apps - XKCD | Calvin | SMBC | Sound Meter | Speed Dial