views:

251

answers:

1

I have a Microsoft Access 2010 database(*). Now, using Visual Studio 2010, I want to create a WPF application and add the database as a data source. The app will have a window with a frame that provides navigation through pages. No problem so far. But:

-What is the right way to set up the database in this scenario? Tables only? Or must everything go via queries? (VS2010 talks about views which I assume (?) are queries)

-Database data must be updatable and records can be added. Some relationships go through link tables (many-to-many) and there are nullable foreign key relationships. Must I take manual steps to make it work?

-While adding the data source VS2010 created an xsd from my Access database. I think the xsd might need further tweaking for the application to work the right way. What if I change my Access database design, I'd have to regenerate the xsd again as well. Is this right, and is it the way it is usually done? OR, should I let the original Access database go and give the application the capability to create new empty databases?

-How do you provide controls in a page to step through the records in a table? Is there a special database control?

-What is the way (WPF class?) to load records into the data context that displays in a page? (At this level it probably does not matter what type of data source it is.)

(*) A single user desktop database

A: 

This is not the exact answer to the question. But an alternative.

A single user desktop database???

You can better try this highly efficient combination:

You should also take a look at ObservableCollection, DataBinding and DataGrid in WPF toolkit

Veer
Thanks for the suggestion! I'm already looking into it.
Kay Zed
I posted a new question based on this. Thanks again.
Kay Zed
Will the DownVoter comment here???
Veer
The answer to question of the form "how do I do X" is not "switch from X to Y." I'm adding my own downvote. The only way you can legitimately evade answering the question by recommending a switch is if you explain why switching is the best solution.
David-W-Fenton
@David-W-Fenton: I know this is a "how do I this" kind of question. That's why I've clearly written it is an alternative since giving the solution to this question may lead the QA to stick to access db. Regarding the explanation for recommendation, I think I've provided enough links in my answer. Further, a hint is enough for the QA to browse through the web rather than an entire list of advantages and disadvantages. This is proved by the comments of the QA to my answer.
Veer