'minor' change - major hassle

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database set up which tracks the recruitment and selection process.

I have been asked to change the way in which the vacancies are numbered.
Originally, the unique vacancy number(PK)was entered manually (it was a
combination of postID and date). However, this was not working for the
administrator so I was asked to change the vacancy number to an autonumber. I
did this by keeping the original field and making a new field an autonumber
and PK field. The system autonumbered all the existing records which was
fine.

However, the problem comes when I try to add this table and its new field in
to a query.

the first query worked well and I based a form on it which was good.

However, If I change the query to include the changed tables, I get an non
updateable dataset.
I have also changed the relationship in the backend to use the new field as
the linked field.

I am stumped as the changes seemed to be fairly minor.

I can paste the sql statements of the working query and the non working
query if required, but I can see little different between them.

What am I missing???

PS all the changes have been done on a copy of the database-luckily!
 
Back
Top