Joe Mamma Posted June 15, 2004 Posted June 15, 2004 in a nutshell. . . Product: Defense Contract Document Control Software System Functionality: Manage Personnel and and their Security Clearences. Verify Personnel to Document Access Requirements Track Personnel Edits on Restricted Documents Verify Personnel to Facility Access Requirements Track Personnel Visits to Restricted Facilities Platforms SQL Server 2000 backend Win2000/XP with MDAC Clients Client wants to internet enable their data access and use the existing VB6 GUI's I am presented with a huge, poorly written VB6 application. 100+ Poorly designed forms with SQL code contained in the .frm file Lots of global Variables. None of the controls are data bound. they pull the string out of the recordset and put it in the control manually. Simply put I dont want to rewrite their entire app in .NET at this time. . . Just create a set of .NET Web services that will return all the recordsets they use to populate their forms and has methods/objects for performing inserts, updates and deletes. The entire application needs a rewrite but that is out of the question. How would you guys approach this scenario??? Quote Joe Mamma Amendment 4: The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no warrants shall issue, but upon probable cause, supported by oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. Amendment 9: The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people.
Joe Mamma Posted June 15, 2004 Author Posted June 15, 2004 Continued. . . So after some research, here is what I am thinking of doing: 1. Create a webservice for each SQL Select statement that takes a set of parameter Name/Value pairs if needed. that returns a typed dataset. 2. Have a client side VB.NET COM object that is loaded into the VB6 App that will have a Method with the following signature: Public Function GetRecordset(ServiceID$, ParamNameValueList as Object) as ADODB.Recordset 3. The client makes the WebService request for the typed dataset specified by ServiceID$ and passes the ParamNameValueList which is used by the web service to Limit the dataset returned. 4. The typed Dataset is returned to the client and saved to disk as XML. 5. A New ADODB.Recordset is created that opens the xml from step 4 and is returned to the calling application. the saved XML from step 4 is deleted A similar set of services will be written for Updates, Inserts and deletes, though thes will not need recordsets returned. . . . Any Thoughts??? Quote Joe Mamma Amendment 4: The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no warrants shall issue, but upon probable cause, supported by oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. Amendment 9: The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people.
Administrators PlausiblyDamp Posted June 15, 2004 Administrators Posted June 15, 2004 It may be worth having a look at The Soap Toolkit from MS - it is a COM component that gives basic Webservice functionality. It could save you a bit of time in getting VB6 to talk to a webservice rather than writting your own COM Dll and the intermediate saving XML to disk step. Haven't used it myself for a long time but thought you would appreciate anything that might stop you having to do too much VB6 :) Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.