Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFPOleDb.1, the day after
Message
From
09/10/2006 07:34:11
 
 
To
08/10/2006 10:28:39
General information
Forum:
ASP.NET
Category:
Databases
Environment versions
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01160349
Message ID:
01160487
Views:
12
>
>Yes, correct, when I ran more tests, at one occurence, it took 3 tries before the attempt was a success. But, again, on the user side, it was ok. I also dropped the number of occurences to 4 and increased the delay to 0.5 second.

I've been thinking of the performance implications a bit. Dropping to 4 seems to allow for errors to crop up sometime and setting it higher won't hurt performance overall as long as the errorlevel stays at a low percentage.

As this handles about 95% of your total SQL, having the critical insert/update/delete run slower might be ok if the changes are not too great (allowing for a quick port back if the issue is resolved).

If I understood ASP.Net Side-by-Side correctly, you cannot force different runtimes directly inside a ASP.Net-process:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconaspnetside-by-sideoverview.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpcondeterminingwhatversionofruntimetoload.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconfiguringassemblybindingredirection.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconmanagingmultipleversionsofaspnet.asp

but I have not seen any clear indication if it is totally impossible to call up a .net 1.1 dll wrapped inside a COM-interface either directly or indirectly or perhaps only in/through another process from ASP.NET 2.0. IF the problem lies in the communication between .net 2.0 and OLEDB, using the OLEDB-Adapter wrapped inside a .Net 1.1-hosted DLL might stop the errors for those critical 5% while keeping the speed of for the other 95% using the errorchecking. The worst case scenario from a perfromance point of view would be to replace your .net2 OleAdapter with a call to a vfp.exe or C/C++.Exe calling up a .net 1.1 OleAdapter - but as this happens only in those 5 percent perhaps not crippling, if it works.

As only the OleDbAdapter would be used in the .Net 1.1 - level the changes should not be too drastic. Be sure to read up before trying, this is something I only read about and have no practical expirience! I might have misunderstood the docs...

regards

thomas
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform