An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
Is there only going to be one edit control in your application that connects? Give it a CDatabase.
Are there going to be lots of edits connecting to a database? Give them each a recordset and connect them to a common CDatabase.
Are you only going to be viewing text, or will you need to handle booleans and integers and dates etc? You'll need some validation, or else you'll get lots of "update failed" notifications from the database, which wouldn't be best practice.
This is only the beginning. You're asking a lot - perhaps you'd like to narrow it down a bit?