C
Clive Long,UK
Hi,
We have an Excel spread-sheet that basicaly integrates the data
from some "point" applications. A user has to retype data into the
spreadsheet - none of the "point" applications can enter data in the
spreadsheet automatically
This Excel spread-sheet is shared between several users and only
one can open spreadsheet for update at any time - and this slows up
the working process a lot.
We are going to migrate the "point" applications to some database
based products, but in the short term is it possible to move the
spreadsheet data into a table in a SQL server database- so that
multiple users can access the table concurrently and add and update
new records simultaneously? We are not adding any new database rules -
essentially the data from the spreadsheet "logically" remains a "flat
file".
I know this is a woeful underuse of SQL Server capability but I
need a quick fix to a data access problem while we work on delivering
the "real" solution.
Thanks
Clive
We have an Excel spread-sheet that basicaly integrates the data
from some "point" applications. A user has to retype data into the
spreadsheet - none of the "point" applications can enter data in the
spreadsheet automatically
This Excel spread-sheet is shared between several users and only
one can open spreadsheet for update at any time - and this slows up
the working process a lot.
We are going to migrate the "point" applications to some database
based products, but in the short term is it possible to move the
spreadsheet data into a table in a SQL server database- so that
multiple users can access the table concurrently and add and update
new records simultaneously? We are not adding any new database rules -
essentially the data from the spreadsheet "logically" remains a "flat
file".
I know this is a woeful underuse of SQL Server capability but I
need a quick fix to a data access problem while we work on delivering
the "real" solution.
Thanks
Clive