Posted by Beowulf on 04/24/06 20:45

I inherited an existing database application about 6 months ago. I've
finished converting it to use SQL Server 2000 as the backend (MS Access
2002 frontend w/ Userforms+VBA code pointing to the backend).

In its current state the application makes use of a ton of embedded SQL
statements and I'm thinking about the best way to clean this up. It
seems like the best way would probably to encapsulate each of the SQL
statements into its own stored proc and then have the MS Access
application call the sp. However, this would result in a very large
number of stored procedures.

Anyone have any links or suggestions regarding best practices on
removing embedded SQL scattered throughout a DB app? Thanks.

• Next in forum: Re: Order by in a INSERT INTO..SELECT
• Prev in forum: Re: No distinct in a select into stement ?
• Thread view: Removing embedded SQL from database application

[Reply to this message]