Cannot open SQL Server Table

Hello,
Can a SQL Server table become corrupted? The tables are linked to an Access
DB and I cannot open the main Order table from Access. I am connected to
the system remotely via Terminal Server and do not have Enterprise manager
available.
I can't imagine what the issue could be otherwise and hope someone can help
me.
God Bless,
Mark A. SamHi Mark,
Yes a SQL-Server table can become corrupted, any file can. If you haven't
patched it, it can also be suseptable to a serious virus. The worst
corruption I have ever seen has been in SQL-Server tables, but it is less
likely than with a file server database like Access.
Try building a new Access database (an MDB, not an ADP) then set up an ODBC
connection (not OLEDB) then try to connect the database to the SQL-Server
tables. I have had some success that way.
I then build make table queries in the MDB and import all the data. I can
then build a new SQL-Server database and export the Access data back into
it. If you don't have a backup, that's your best hope.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:eC7zX1D9DHA.2924@.tk2msftngp13.phx.gbl...
> Hello,
> Can a SQL Server table become corrupted? The tables are linked to an
Access
> DB and I cannot open the main Order table from Access. I am connected to
> the system remotely via Terminal Server and do not have Enterprise manager
> available.
> I can't imagine what the issue could be otherwise and hope someone can
help
> me.
> God Bless,
> Mark A. Sam
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.587 / Virus Database: 371 - Release Date: 2/12/2004|||Thanks Arvin,
This is an .mdb with linked tables. I already tried importing and it didn't
work. I think my client switched to SQL Server because the Access backend
was always becoming corrupted and he thought SQL Server tables were more
stable. It cost him a bundle for me to convert the code even for linked
tables. It was a bear. All I can hope is that he had a tape backup. I set
up an backup on thwe server and don't recall if I have it for a couple days
back, but think I may. I quit this business as of last week and thought I
was free from this nonsense. Sheesh.
Believe it or not, in retrospect the data was more secure with the Access
Backend. I kept multiple backups as well as a procedure to copy the tables
during the day. It isn't as easy to back up SQL Server tables.
Thanks Arvin,
God Bless,
Mark
"Arvin Meyer" <a@.m.com> wrote in message
news:ukN3zOE9DHA.3348@.TK2MSFTNGP09.phx.gbl...
> Hi Mark,
> Yes a SQL-Server table can become corrupted, any file can. If you haven't
> patched it, it can also be suseptable to a serious virus. The worst
> corruption I have ever seen has been in SQL-Server tables, but it is less
> likely than with a file server database like Access.
> Try building a new Access database (an MDB, not an ADP) then set up an
ODBC
> connection (not OLEDB) then try to connect the database to the SQL-Server
> tables. I have had some success that way.
> I then build make table queries in the MDB and import all the data. I can
> then build a new SQL-Server database and export the Access data back into
> it. If you don't have a backup, that's your best hope.
> --
> Arvin Meyer, MCP, MVP
> Microsoft Access
> Free Access downloads:
> http://www.datastrat.com
> http://www.mvps.org/access
> "Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
> news:eC7zX1D9DHA.2924@.tk2msftngp13.phx.gbl...
> Access
to
manager
> help
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.587 / Virus Database: 371 - Release Date: 2/12/2004
>|||This is not true:
"It isn't as easy to back up SQL Server tables."
SQL Server is extremely simple to backup.
--
Joe Fallon
Access MVP
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:evcjokE9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> Thanks Arvin,
> This is an .mdb with linked tables. I already tried importing and it
didn't
> work. I think my client switched to SQL Server because the Access backend
> was always becoming corrupted and he thought SQL Server tables were more
> stable. It cost him a bundle for me to convert the code even for linked
> tables. It was a bear. All I can hope is that he had a tape backup. I
set
> up an backup on thwe server and don't recall if I have it for a couple
days
> back, but think I may. I quit this business as of last week and thought I
> was free from this nonsense. Sheesh.
> Believe it or not, in retrospect the data was more secure with the Access
> Backend. I kept multiple backups as well as a procedure to copy the
tables
> during the day. It isn't as easy to back up SQL Server tables.
> Thanks Arvin,
> God Bless,
> Mark
>
>
> "Arvin Meyer" <a@.m.com> wrote in message
> news:ukN3zOE9DHA.3348@.TK2MSFTNGP09.phx.gbl...
haven't
less
> ODBC
SQL-Server
can
into
> to
> manager
>|||Hello Joe,
Easier then copy and paste or click a button?
The backup was fine when I set up last summer. But when I tried to restore
what was there wasn't what I set it up to be. There were folder files which
should have been deleted and the newer files that were expected didn't
exist. I had set up one profile to backup every Sunday and delete copies
older than two weeks. There were three copies available for restoring, one
from mid January and two from December. I also have a package which
exported the tables to a test Db every morning. The tables pertaining to
orders were all empty in that database. It seems that one needs to be a
technically minded genius to deal with this stuff. I'm far from it. ;)
God Bless,
Mark
"Joe Fallon" <jfallon1@.nospamtwcny.rr.com> wrote in message
news:uw7nQFP9DHA.3404@.TK2MSFTNGP09.phx.gbl...
> This is not true:
> "It isn't as easy to back up SQL Server tables."
> SQL Server is extremely simple to backup.
> --
> Joe Fallon
> Access MVP
>
> "Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
> news:evcjokE9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> didn't
backend
> set
> days
I
Access
> tables
> haven't
> less
> SQL-Server
> can
> into
an
connected
can
>