Home/ Questions/Q 920061
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T18:38:50+00:00

I am looking for a quick way of enabling data entry to a well

  • 0

I am looking for a quick way of enabling data entry to a well structured SQL database.

We have defined all our data entry rules (by that I meean validation, mandatory fields etc.) and we’re now looking for a tool to make it as easy as possible to have this database populated.

The database is largely product orientated, so the ability to add/edit products is important. Whenever a change to a field is made, it should be validated against the data rules to ensure it ‘makes sense’ before being written to the database. The ability for us to run reports on historical information is important, so the database must hang onto all of the products historical attirbutes too.

Eventually this data will be used for some standard reporting, and will be made available via a dashboard style reporting service that we will one day be able to afford! (hopefully)

Would Infopath be a good way of doing this? Are there any articles around the place that discuss a similar approach and how they were able to do it?

If not, what would users here suggest?

Background: I am from a business/product background and am trying to do some leg work myself to get a good outcome.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Regarding Infopath – I think it will depend on the complexity of your rules.

    Regardless, you will need your database design to be able to record history – have you already determined a database design which is able to meet your requirements for storing the historical attributes?

    You should consider your business requirements for reporting and any point-in-time consistency and the architecture should follow. Like you said, you’ve got a proper IT guy, so if you’ve got your business rules all sorted out, they should be able to critically evaluate it and expose any things you haven’t thought about. I’ve become a big fan of having a transactional operational database (perhaps retaining full history, but not providing rich access to it) with limited reporting capabilities and a reporting database with a model (like Kimball’s dimensional data warehouse) conducive to point-in-time reporting etc.

    • 0