S
Scott Clifford
Can anyone help me get to the bottom of what looks like
misbehaviour by Access. Apologies if this is a long story.
I'm developing an application in Access 2000 for a charity
to replace one they inherited written in FileMaker Pro
4.1. So far I'm writing a VB6 routine to import the data,
using ADO 2.1.
There's a good few tables (~30) including one which
started life as tblMember which I renamed tblMembership.
Being an orderly cove I also renamed the primary key from
MemberID to MembershipID. Also I added a field,
MemberClassID.
I'm trying to populate tblMembership using an ADO
recordset as I've done countless times before, including
several times in my import procedure.
And here's the problem. When I try and set the value of
the MemberClassID field I get the error 3265 item can't be
found in the collection.
Using the immediate window I have gone through the fields
collection (?rsTemp.fields(0).name) and it isn't there.
But when I open the table in design mode it is.
I also happened to notice that the primary key is still
called MemberID, though again in design view it appears as
MembershipID.
So, somehow the table definition as seen by ADO is
corrupt. I've tried all I can think of to get round
this. I shut down Access and reopened. I repaired and
compacted the database. I rebooted windows. I made a new
blank database and imported all the objects from the
original - still ADO thinks the primary key is called
MemberID and cannot find MemberClassID at all.
Help, please.
Scott
misbehaviour by Access. Apologies if this is a long story.
I'm developing an application in Access 2000 for a charity
to replace one they inherited written in FileMaker Pro
4.1. So far I'm writing a VB6 routine to import the data,
using ADO 2.1.
There's a good few tables (~30) including one which
started life as tblMember which I renamed tblMembership.
Being an orderly cove I also renamed the primary key from
MemberID to MembershipID. Also I added a field,
MemberClassID.
I'm trying to populate tblMembership using an ADO
recordset as I've done countless times before, including
several times in my import procedure.
And here's the problem. When I try and set the value of
the MemberClassID field I get the error 3265 item can't be
found in the collection.
Using the immediate window I have gone through the fields
collection (?rsTemp.fields(0).name) and it isn't there.
But when I open the table in design mode it is.
I also happened to notice that the primary key is still
called MemberID, though again in design view it appears as
MembershipID.
So, somehow the table definition as seen by ADO is
corrupt. I've tried all I can think of to get round
this. I shut down Access and reopened. I repaired and
compacted the database. I rebooted windows. I made a new
blank database and imported all the objects from the
original - still ADO thinks the primary key is called
MemberID and cannot find MemberClassID at all.
Help, please.
Scott