No, that wouldn't work. The process is...
1. New record is created OR Existing record is opened
2. User inputs changes
3. User hits "Calculate" button. VBScript auto-fills as many fields as it
can.
4. User overrides any values they need to.
5. User hits "Save" button. VBScript validates form.
6. Data is sent to the database.
Each form has its own rules, and those rules change on a regular basis.
(When I say form, I mean it in the generic sense. I have a single VB Form
that uses info in the database to create the form.)
Jonathan
"Chris, Master of All Things Insignificant" <chris@No_Spam_Please.com> wrote
in message news:%2****************@TK2MSFTNGP11.phx.gbl...
Can you do it as a stored procedure? This seems like a better more
efficient way of going about it.
Chris
"Jonathan Allen" <x@x.x> wrote in message
news:eL****************@TK2MSFTNGP11.phx.gbl... With VB6, I stored a lot of user-defined business rules in a database as
VBScript. The VB application would load and run the script as needed.
They were fairly simple, mainly field validation.
Is there a way to do this in VB.Net? (I am willing to use VB.Net instead
of VBScript, so long as I can still store it as clear text rather than in
a compiled form.)
Jonathan