Hi Cindy, thanks for your response...
My fox database is firing the delete trigger... and i need it.
my original problem is an oleDb limitation... Oledb not support delete
trigger.
In order to evade this problem i build a single vfox class, heres the
code:
DEFINE CLASS IventaDB AS Session OLEPUBLIC
FUNCTION doNonQuery (strSentence as String, rutaDb as String)
result="ok"
try
OPEN DATABASE &rutaDb SHARED
strSentence =strSentence
&strSentence
CLOSE DATABASES
CATCH TO errorRes
result=errorRes
ENDTRY
RETURN result
ENDFUNC
ENDDEFINE
And my actual problem is that i can't isolate my vfoxDll generated and
the host machine says need to register it... and when i build my
project on VS2005 i have a warning
Warning the 1 assembled one to which reference becomes
"c:\project\bin\debug\Native.EysComunicaWin.manife st" applies to a
processor different from the one of the application. EysComunicaTray
there's one Solution named EysComunica.
there's two Projects
- EysComunicaTray is an WinForm Application.
- EysComunicaWin is an Class Library Application.
EysComunicaWin has a reference to Interop.COMvfoxDLL.dll and has set
"Isolated" property value to True.
im installing using clickonce technology, is required.
Cindy Winegarden wrote:
Hi Celerno,
Aside from your question about registering the DLL, what sort of triggers
are firing and how have you written the DLL code that it can delete rows and
not fire the triggers?
--
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
ci***@cindywinegarden.com
"celerno" <ce*****@gmail.comwrote in message
news:11*********************@b28g2000cwb.googlegro ups.com...
Hi all, first some history: i'm developing an application who access
foxpro databases using VfpOledb provider... but this cause a headache
when i delete rows cause some tables call triggers... to fix it... or
to find other way i make a dll class in vfpro in order to use some
database and execute some delete sql.
function execSql(string database,string sqlSentence);