Re: URGENT: FoxPro COM Object

From: Anders Altberg (x_pragma_at_telia.com)
Date: 09/11/04 

Date: Sat, 11 Sep 2004 16:13:32 +0200

RI trigger code, validation rules, and database events will run whether you
execute queries from an ADODB connectrion or through a native VFP
application, or even the VFP IDE. They are there to protext the data from
possible harm
-Anders

"Faraz Khan" <faraz.khan@ezdoc.net> wrote in message
news:a75fab3a.0409102102.5758254@posting.google.com...
> Please Please Please. I am in time crunch and need to have fast access
> to a FoxPro database (*.dbc file). Thru VB, I tried using both OLE-DB
> and ODBC drivers for fox pro to insert/update data in that database.
> However, there are certain code in the foxpro triggers and field
> validation rules that are not supported under ODBC or OLE-DB. So my
> app fails.
>
> Up until now I have been editing the stored procedures in foxpro to
> comment out the incompatible code that causes the problem. But I can
> no longer do that. The 3rd party app which has the foxpro DB has been
> updated in such a way that changing the stored procedures codes will
> break the 3rd party app, which is not an option anymore.
>
> Someone suggested creating a very simple 1 method COM object using
> foxpro. Thet single method will take a string as input and return a
> ADO25.Recordset object. The method will exeucte ANY sql passed to it
> after connecting to the DBC file. Since the method is written in
> foxpro it should have no problems with the stored procedures within
> the DBC. Is this possible??
>
> Please help me write this COM object. I have no idea what to do or
> how to begin. Please keep in mind that this COM object must not have
> any GUI, since its has to run in ASP, ASP.NET as well as VB.NET
> console app as a batch.

Relevant Pages

  • Re: URGENT: FoxPro COM Object
    ... execute queries from an ADODB connectrion or through a native VFP ... > Up until now I have been editing the stored procedures in foxpro to ... > break the 3rd party app, which is not an option anymore. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: URGENT: FoxPro COM Object
    ... execute queries from an ADODB connectrion or through a native VFP ... > Up until now I have been editing the stored procedures in foxpro to ... > break the 3rd party app, which is not an option anymore. ...
    (microsoft.public.fox.helpwanted)
  • URGENT: FoxPro COM Object
    ... to a FoxPro database (*.dbc file). ... I tried using both OLE-DB ... there are certain code in the foxpro triggers and field ... break the 3rd party app, which is not an option anymore. ...
    (microsoft.public.fox.helpwanted)
  • URGENT: FoxPro COM Object
    ... to a FoxPro database (*.dbc file). ... I tried using both OLE-DB ... there are certain code in the foxpro triggers and field ... break the 3rd party app, which is not an option anymore. ...
    (microsoft.public.fox.vfp.dbc)
  • URGENT: FoxPro COM Object
    ... to a FoxPro database (*.dbc file). ... I tried using both OLE-DB ... there are certain code in the foxpro triggers and field ... break the 3rd party app, which is not an option anymore. ...
    (microsoft.public.fox.programmer.exchange)
Loading