M
Mike
I've seen this sort of answered earlier, but would like to be 100%
sure that it's as unlikely as I suspect it is - can .NET create an
"old-fashioned" dll which can be called by 16-bit programs written in
BC5?
We have a hefty db app created with BC5 which uses an xBase data
store. The idea is that since a single dll routes all access between
the business layer and the xBase engine, they can graft
performance&scalability onto this relic by swapping out their dll for
one written in .NET which acceses SQL 2k. Existing 16-bit exe's and
dll's would use exactly the same function calls into this new dll and
be none the wiser.
Sounds like wishful thinking to me, but I'm still a newbie when it
comes to .NET - is this even remotely possible? If it was, would
there be be even greater than normal interop costs? And, (OT I know
but just to cover all bases) can even VB6 go backwards like that?
Thanks - Mike
sure that it's as unlikely as I suspect it is - can .NET create an
"old-fashioned" dll which can be called by 16-bit programs written in
BC5?
We have a hefty db app created with BC5 which uses an xBase data
store. The idea is that since a single dll routes all access between
the business layer and the xBase engine, they can graft
performance&scalability onto this relic by swapping out their dll for
one written in .NET which acceses SQL 2k. Existing 16-bit exe's and
dll's would use exactly the same function calls into this new dll and
be none the wiser.
Sounds like wishful thinking to me, but I'm still a newbie when it
comes to .NET - is this even remotely possible? If it was, would
there be be even greater than normal interop costs? And, (OT I know
but just to cover all bases) can even VB6 go backwards like that?
Thanks - Mike