|
Home > Archive > MS SQL Server > May 2005 > Linking to Tables from Access
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Linking to Tables from Access
|
|
| Declan 2005-05-23, 9:23 am |
| My company uses and heavily relies on Access 97 databases with linked
tables. The tables are contained in Access 97 databases, and these databases
keep becoming corrupt. I realize that if I only import the tables into SQL
Server and link to them without re-writing the front-end Access programs then
I wouldn't be taking full advantage of SQL Server's capabilities, but I need
an immediate solution to this corruption problem and I'm considering this as
an option. After importing linking to the tables, I would gradually, as time
permits, re-write the Access programs to use SQL Server to its full
potential. Now here's my question ... If I import the tables into SQL Server
and link to them from the front-end Access databases, will this prevent the
corruption of data?
| |
| Michael C# 2005-05-23, 9:23 am |
| Depends on the source of the corruption. If the MDB files are getting
corrupted (as they seem to do quite often in multi-user environments), then
your solution will help. If the data in the tables is being corrupted
because of Jet's poor locking mechanisms, then your solution will again help
a little. If the data in the tables is being corrupted because of faulty
program logic, or other errors internal to the front-end program itself,
then your solution won't help at all.
"Declan" <Declan@discussions.microsoft.com> wrote in message
news:8F0A5137-010B-4972-B75A- BCAD4CFB5106@microso
ft.com...
> My company uses and heavily relies on Access 97 databases with linked
> tables. The tables are contained in Access 97 databases, and these
> databases
> keep becoming corrupt. I realize that if I only import the tables into
> SQL
> Server and link to them without re-writing the front-end Access programs
> then
> I wouldn't be taking full advantage of SQL Server's capabilities, but I
> need
> an immediate solution to this corruption problem and I'm considering this
> as
> an option. After importing linking to the tables, I would gradually, as
> time
> permits, re-write the Access programs to use SQL Server to its full
> potential. Now here's my question ... If I import the tables into SQL
> Server
> and link to them from the front-end Access databases, will this prevent
> the
> corruption of data?
| |
| Dan Guzman 2005-05-23, 9:23 am |
| > Now here's my question ... If I import the tables into SQL Server
> and link to them from the front-end Access databases, will this prevent
> the
> corruption of data?
SQL Server is more reliable than Access in this area and provides more
robust backup and recovery options. You still need to implement a
backup/recovery plan, though.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Declan" <Declan@discussions.microsoft.com> wrote in message
news:8F0A5137-010B-4972-B75A- BCAD4CFB5106@microso
ft.com...
> My company uses and heavily relies on Access 97 databases with linked
> tables. The tables are contained in Access 97 databases, and these
> databases
> keep becoming corrupt. I realize that if I only import the tables into
> SQL
> Server and link to them without re-writing the front-end Access programs
> then
> I wouldn't be taking full advantage of SQL Server's capabilities, but I
> need
> an immediate solution to this corruption problem and I'm considering this
> as
> an option. After importing linking to the tables, I would gradually, as
> time
> permits, re-write the Access programs to use SQL Server to its full
> potential. Now here's my question ... If I import the tables into SQL
> Server
> and link to them from the front-end Access databases, will this prevent
> the
> corruption of data?
| |
| Jens Süßmeyer 2005-05-23, 9:23 am |
| You could also have (in addition to the other posts) trouble with updating
data on the SQl Server due to the complexity for Access identifying the rows
that are affected by an update. But if you run into those problems, there
are many samples there outside guiding you the way out of that problem. Even
some of the DAO (if you are using that) function might won´t work with the
porting to the SQL Server, but its even worth a try.
--
HTH, Jens Suessmeyer.
---
http://www.sqlserver2005.de
---
"Declan" <Declan@discussions.microsoft.com> schrieb im Newsbeitrag
news:8F0A5137-010B-4972-B75A- BCAD4CFB5106@microso
ft.com...
> My company uses and heavily relies on Access 97 databases with linked
> tables. The tables are contained in Access 97 databases, and these
> databases
> keep becoming corrupt. I realize that if I only import the tables into
> SQL
> Server and link to them without re-writing the front-end Access programs
> then
> I wouldn't be taking full advantage of SQL Server's capabilities, but I
> need
> an immediate solution to this corruption problem and I'm considering this
> as
> an option. After importing linking to the tables, I would gradually, as
> time
> permits, re-write the Access programs to use SQL Server to its full
> potential. Now here's my question ... If I import the tables into SQL
> Server
> and link to them from the front-end Access databases, will this prevent
> the
> corruption of data?
| |
| Mike Epprecht (SQL MVP) 2005-05-23, 9:23 am |
| Hi
Since Access 97 support was ended 31 Jan 2004 by Microsoft, I would
recommend that you upgrade your version too.
http://support.microsoft.com/gp/lifeofficefam
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jens Süßmeyer" wrote:
> You could also have (in addition to the other posts) trouble with updating
> data on the SQl Server due to the complexity for Access identifying the rows
> that are affected by an update. But if you run into those problems, there
> are many samples there outside guiding you the way out of that problem. Even
> some of the DAO (if you are using that) function might won´t work with the
> porting to the SQL Server, but its even worth a try.
>
> --
> HTH, Jens Suessmeyer.
>
> ---
> http://www.sqlserver2005.de
> ---
> "Declan" <Declan@discussions.microsoft.com> schrieb im Newsbeitrag
> news:8F0A5137-010B-4972-B75A- BCAD4CFB5106@microso
ft.com...
>
>
>
|
|
|
|
|