Thanks for the reply. I guess I've got some reading to do, but that's what
lunch break is for, I suppose. I'll leave a reply in this thread as to what
the cause was, just in case you're interested.
Thanks again...
--
Kevin Backmann
"Brendan Reynolds" wrote:
> Using a bigint field as the primary key in SQL Server will do this, but
> there are other possible causes too. Check out some of the articles in the
> list at the following URL ...
>
> http://search.msdn.microsoft.com/sea...ked+%23Deleted
>
> --
> Brendan Reynolds
> Access MVP
>
> "Kevin B" <(E-Mail Removed)> wrote in message
> news:84B58A53-8C39-40B2-B8F3-(E-Mail Removed)...
> >I am connecting via ODBC to a number of tables in a database, located on an
> > SQL server. One of the tables that I'm linking to is a table that is
> > updated
> > automatically via DTS with the update kicked off by a VB script.
> >
> > On the Access side, if I view this table all I see are #Deleted flags in
> > all
> > fields, even though there is data in the table if I view it from SQL
> > Enterprise Manager. All other ODBC linked tables display data correctly.
> >
> > If done a refresh links in Access, removed and reestablished the link to
> > the
> > table, and that has not rectified the problem. If I run a query, report,
> > or
> > view the table through a form in Access all I get is #Deleted. However,
> > if I
> > export this table from Access to Excel I get all of my records exported.
> >
> > Anyone out there encounter this problem before, or is there something I've
> > overlooked?
> >
> > Thanks ahead of time.
> >
> > --
> > Kevin Backmann
>
>
>