Calling a Windows DLL
From: Alan (apayne_at_defcon-hq.com)
Date: 05/28/04
- Previous message: Mark Rafn: "Re: fork and process timing issue"
- Next in thread: David Schwartz: "Re: Calling a Windows DLL"
- Reply: David Schwartz: "Re: Calling a Windows DLL"
- Reply: Ian: "Re: Calling a Windows DLL"
- Reply: Lew Pitcher: "Re: Calling a Windows DLL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 May 2004 12:56:07 -0700
We have a windows application written in VB w/SQL Server (SQL2K) in
the backend. Another application would like to have access to some of
our data (read/only). Normally we would provide the data via our
external interface DLL, but this is a Java application is running on
Unix. We really don't want the java app hitting the database directly
(even R/O) because when things change their app would then be broke
and we get yelled at.....
In the Windows world we simply make sure our external interface DLL
doesn't change input or output interfaces and we make all necessary
chages to the DLL behind the scene. Any suggestions on how best to
approach this? We would like to maintian the interface layer since our
developers are most familar with the application and database.
- Previous message: Mark Rafn: "Re: fork and process timing issue"
- Next in thread: David Schwartz: "Re: Calling a Windows DLL"
- Reply: David Schwartz: "Re: Calling a Windows DLL"
- Reply: Ian: "Re: Calling a Windows DLL"
- Reply: Lew Pitcher: "Re: Calling a Windows DLL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
