| Subject: Dynamic Data Access Layer |
| Group: microsoft.public.vstudio.general |
| Date: 7/17/2008 4:52:50 PM |
| From: "jmancuso via DotNetMonster.com" [Email Address Protection] |
I haven't worked a lot with .NET in last couple years so am a bit rusty, please excuse me. I'm trying to design a system that is flexible enough to execute a variety of different SQL procedures based on a selected Job. To clarify, if Job A is run I would like to execute Procedure 1 & 2. If Job B is run I'd like to execute Procedures 1 & 3. If an administrator wanted to create a new Job C that used Procedures 3 & 4. They would be able to manage this within the SQL tables. So what I'm thinking is creating a data access layer that can dynamically change. I'd have a class with a couple methods, one method might return a collection of procedures and their parameters based on a job passed to the method. These procedures then would act like their own data access methods. i.e. public GetProcedures (int jobID); //returns procedure named Procedure1 There'd then be another method: public [Procedure Name returned from GetProcedures] ([Parameters returned from GetProcedures); Is something like this even possible? Would something like this makes sense? What I'm trying to get at is avoid having developers update .net methods/code each time a new type of job is created requiring a different set of processes to be run. Any direction or advice will much be appreciated. Thanks. -- Message posted via DotNetMonster.com http://www.dotnetmonster.com/Uwe/Forums.aspx/mvs-general/200807/1 |
| Back |