June 10, 2005 at 9:13 am
We have a VBA application in an Access 2000 database. When invoked it reads through a 10 milion row table sequentially and updates 2 columns based on the contents of other columns.
The application needs moving to SQL Server 2000, which is where the table now lives. What we don't want is to bring the data into Access in order that it can be processed by the existing VBA app, unless we have to.
We're trying to re-code the VBA to run as a back-end process on SQL Server. However, the logic demands that we process the table sequentially, a record at a time.
What is the best way to achieve server-based VBA-style sequential processing in SQL Server 2000?
June 10, 2005 at 9:51 am
Create an access data project. It'll use sqlserver to store the data. But you'll be able to access it as if it were residing in access.
What's the task that needs to be done sequentially? Maybe we can show you how to do it in a single query.
June 10, 2005 at 10:05 am
We don't want to access the data in SQL Server from an Access application. We want to run a server-based process that reads, and updates, a table sequentially in SQL Server 2000.
June 10, 2005 at 10:08 am
What are you trying to do exactly in the server side process?
Can you show the before and after versions of the data?
June 13, 2005 at 2:51 am
Let's just assume, for now, that it can't be done in SQL.
What choices do I have?
June 13, 2005 at 6:27 am
Open a connection to the server, fetch the data and do whatever you have to do to it.
Check http://www.Connectionstrings.com
BTW I haven't found anything that is NOT possible to do in TSQL. What can be so hard that it cannot be done server-side??
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply