Re: Linking SQL Server 2000 to Access - Bigint datatype
From: Ken McAndrew (kmcandrew_at_infoconcepts.com)
Date: 04/02/04
- Next message: DTHMTL: "Re: Recordset Questions"
- Previous message: Brian Moran: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- In reply to: Brian Moran: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- Next in thread: Sue Hoegemeier: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 2 Apr 2004 10:40:29 -0500
I'm using Access 2003 to generate the database, but it's in Access 2000
format. I did try converting it to Access 2002-2003 format using the
database utilities, but it had the same problems.
-- Kenneth S. McAndrew Software Developer, Information Concepts kmcandrew@infoconcepts.com "Brian Moran" <brian@solidqualitylearning.com> wrote in message news:O7cd0PMGEHA.3568@tk2msftngp13.phx.gbl... > What version of Access are you using? I hadn't known about this particular > issue, but I can understand why it's happening. Perhaps a newer version of > Access knows about BIGINT? Although that may not be a viable solution for > you anyway? > > -- > > Brian Moran > Principal Mentor > Solid Quality Learning > SQL Server MVP > http://www.solidqualitylearning.com > > > "Ken McAndrew" <kmcandrew@infoconcepts.com> wrote in message > news:ej4kwpLGEHA.740@tk2msftngp13.phx.gbl... > > I'm currently trying to create an Access database that has links to SQL > > Server views, so that end users can directly edit their data. When I link > > these SQL views into Access, however, I'm given the "#DELETED" message > > across all my rows. I've narrowed down the issue to the bigint datatype; > it > > appears that Access is not equipped to handle it. I tried this in both an > > Access 2000 and Access 2002-2003 format database. > > > > One of my colleagues suggested using a CAST to change the datatype of the > > bigint to an int [CAST(<field> as int)], which works fine for display > > purposes, the SQL view comes up in Access. However, when I attempt to edit > > the data, I get the following message: > > > > Update or insert of view or function '<name>' failed because it contains a > > derived or constant field. (#4406) > > > > In doing a Google search, I found the MySQL ODBC connector program has a > > "convert bigint to int" option, but a similar tool doesn't seem to exist > in > > the Microsoft ODBC administrator. > > > > Does anyone have any ideas on how to make this viable? > > > > Thanks. > > > > -- > > > > Kenneth S. McAndrew > > Software Developer, Information Concepts > > kmcandrew@infoconcepts.com > > > > > > > >
- Next message: DTHMTL: "Re: Recordset Questions"
- Previous message: Brian Moran: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- In reply to: Brian Moran: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- Next in thread: Sue Hoegemeier: "Re: Linking SQL Server 2000 to Access - Bigint datatype"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|