Re: DB Processing Question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



It depends on the complexicity of the checks and the size of the data.

In general u choose sql to perform the checks because its much faster ( and
'portable' to sqlserver e.g.) but u loose very sopfisticated error
reporting.

Martin

"George" <George@xxxxxxxxxx> schreef in bericht
news:OArLzFTyFHA.2960@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I am trying to write an VB6 application that updates a main access db
table
> with monthly access db table update. In this update I need to apply
> business rules to this data before the update. I understand how to
> accomplish the business rules of the project but was wondering if using
ADO
> and VB6 to import the data is a wise decision. Any ideas or suggestions
to
> help start on this project?
>
> Thanks
>
>


.



Relevant Pages

  • Re: DB Processing Question
    ... > table with monthly access db table update. ... > business rules to this data before the update. ... > ADO and VB6 to import the data is a wise decision. ... more details it's hard to make any kind of decent suggestion. ...
    (microsoft.public.vb.general.discussion)
  • DB Processing Question
    ... I am trying to write an VB6 application that updates a main access db table ... with monthly access db table update. ... accomplish the business rules of the project but was wondering if using ADO ... Prev by Date: ...
    (microsoft.public.vb.general.discussion)
  • Re: DB Processing Question
    ... Your plan will work, VB6 and MS Access is used in far more complicated talk ... >>> table with monthly access db table update. ... >>> apply business rules to this data before the update. ...
    (microsoft.public.vb.general.discussion)
  • Re: DB Processing Question
    ... a foxpro table. ... >> apply business rules to this data before the update. ... >> accomplish the business rules of the project but was wondering if using ... >> ADO and VB6 to import the data is a wise decision. ...
    (microsoft.public.vb.general.discussion)