table relationships - weird problem

[David]

Are you sitting comfortably?

I had a table which had relationships defined.
I made a copy of this table (structure only - no data),
then renamed the original and then renamed the copy back
to the original name.
(I wanted a table empty of data).

The relationships looked fine in the diagram.
I started testing and it turned out the table had its
autonumber key defined as number. This must have happened
during the copy/rename.

The original autonumber was set to double and now I only
see long-integer and replication id choices. Double does
not appear. So now I cannot re-establish the relationships
because the linked-to tables are expecting Double

Bear with me....

So, I dropped the relationship and tried to set the column
in the linked-to table to long integer. Lo and behold it
says I can't do it because there is a relationship!!! Even
though I deleted the line in 'table relationships'.

Help!!! I appear to be hopelessly screwed. I'm at a total
standstill. Obviously my copy and rename of a table with
relationships caused Access to get in a twist.

 

[Adrian Jansen]

Something really wierd about your statement

"The original autonumber was set to double "

Autonumbers can only be long int, AFAIK

Maybe this is the cause of all the subsequent problems.
--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

 

[John Vinson]

Something really wierd about your statement

"The original autonumber was set to double "

Autonumbers can only be long int, AFAIK

Maybe this is the cause of all the subsequent problems.

Well, long int or GUID... but you're right, not Double to my
knowledge!

 

[David]

It was set to double.

-----Original Message-----
Something really wierd about your statement

"The original autonumber was set to double "

Autonumbers can only be long int, AFAIK

Maybe this is the cause of all the subsequent problems.
--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control



.

 

[Adrian Jansen]

I would still be very wary of using a database with an existing autonumber
as field type double. That breaks all the rules of number typing.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

 

[Bryan Christopher]

It was set to double.

Yup, something's amiss. How you were able to make an autonumber type
double..?

As far as the haunting relationship, go back into the relationships
window and add the old and new tables back into the relationship
window (show table), chances are you deleted the table from the
relationship window, not the actual relationship. After adding the
old and new table, any residual relationships that are left after the
naming, renaming, swapping fiesta should be evident.