Is this a repost?? As far as suggestions go, 1.1 has pretty nice support for your database connections...if this is only a proof of concept, I would just do something simple with, maybe, an access database...you may also consider using an XML file, since there is nice functionality built already around it. Other than that, it really depends on what kind of "resources" you are looking for. If you're looking for sample code for your individual modules, I would recommend checking out sourceforge. But if you really need to just get started, I would do some research, check out reservation systems that are out there and take into account what you are reserving through them. A few of the things that will almost always be present in a reservation system:
Reservation [start] date - TextBox
[Reservation end date] (for a range) - TextBox
[Calendar] (for easy date selection) - PopupCalendar (But as I said in your last post, try to use a javascript one, as the .NET calendar control is slow)
Name - TextBox(es)
Phone - TextBox
[Address] - TextBox(es)
[E-Mail Address] - TextBox
[CreditCard Payment] - DropList(CardTypes), TextBox (CardNumber), ComboBox(ExpirationMonth), ComboBox(ExpirationYear), [TextBox (CVV#)]
[Billing Address (If Different From Above)] - TextBox(es)
There is a start on some of your basic fields/Control types. Other than these, you'll want:
Validation (Using the native .NET ValidationSummary)
-Date (Text is a valid date)
-Date (Date is before/after your allowed dates)
-Phone
-[Zip]
-[E-Mail]
-[Card Number]
-[CVV]
-[Billing Zip]
-Required Fields Present
Hopefully this will get you started. As for User Experience, that's all you since I don't know your intended demographic or what the industry the system is intended for is.
Good luck,
-Kevin
- "The truth hurts, maybe not as much as jumping on a bicycle with no seat, but it hurts.