Windows XP 
Access 2007
Please bear with me; I've only been learning Access since June, and VBA since August.
I have a couple of database projects I'm doing for work. Database A's primary function is comparing numbers and maintaining a glorified rolodex, but there are rules that may apply per state that the system would have to trigger under certain circumstances (policy renewals, and such). Database B's primary function is to take insurance policy information in from the user, compare it to the rules and the property data, and determine if the coverage is adequade; there are two different sets of rules that can apply depending on the property, and both are highly complex, and subject to change a little bit here and there, and sometimes be completely rewritten (every couple of years or so).
So I heard mention of "Business Rules Engines", and have been doing some research. I'm having a hard time telling from what I'm reading if this is something that I could build into my databases, or if this is something separate? And if it's separate, is it something I could link to Access? And how would I create it? And if I'm moving the back end of my databases into SQL Server, these engines would remain outside of the server with the front ends, correct?
I'm also trying to determine what type of rule engine would be best for either project. A's can be fairly simple, as the only comparisons I know I'll need it to make as of right now are to check the status of the insurance company, and then check what state the property is in to determine if we need to get this or that form signed. B's is going to be highly complex, with the engine working as a very large flow chart; the required coverage type and/or amount can be determined by a multitude of factors, all of which must be analyzed and considered.
I'm thinking Database A's needs could be met with a forward-chaining production/inference rule engine (sound right?). Database B, however, is proving more difficult to determine. My first pick was a backward-chaining/goal-driven engine type, but the Wikipedia description for business rules engine also mentions "Internet Business Logic system" which sounds good, and deterministic engines, which sound even more like what I need until it mentions using domain-specific languages, which I do not know. I'm already learning VBA and SQL, so I really don't want to throw any more languages into the mix, especially since I'm not planning on making a career switch to IT, so I'm not sure that a deterministic engine is right for me, but the article says that it's easier to implement and maintain, and provides performance advantages.
Another thing to consider is I would like for Database B's rules to be updatable by the department supervisor, if possible, rather than me having to go in and recode when rules change (and sometimes, the old rules will need to stay in the system because older accounts may still be using them). Database B is a volunteer project I'm doing for another department, that I'd really like to be able to turn over to them, with as little follow-up needed as possible.
If anyone knows some good resources online or books on the subject, please let me know. I'm trying to find what I can online, but there's so much that doesn't apply to me (or is definitely not geared toward beginners) that I'm having a hard time finding what I need.
Reply With Quote
