I MADE SOME CHANGES, CAN YOU TAKE A LOOK AND GIVE ME YOUR OPINION? "FIRE SERVICE PRO 2.0" IN ASSISTANCE NEEDED
THANKS, EDGAR
--- In MS_Access_Professionals@yahoogroups.com, "John Viescas" <john@...> wrote:
>
> (Name?)-
>
> Yes, you are doing something wrong. AutoNumber, as it's name implies, is a
> numeric field. You cannot create a relationship between that and a text field.
> The Foreign Key field must be a Long Integer.
>
> John Viescas, author
> Microsoft Office Access 2010 Inside Out
> Microsoft Office Access 2007 Inside Out
> Building Microsoft Access Applications
> Microsoft Office Access 2003 Inside Out
> SQL Queries for Mere Mortals
> http://www.viescas.com/
> (Paris, France)
>
>
>
> -----Original Message-----
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of
> the_extinguisher_pro
> Sent: Tuesday, May 31, 2011 12:51 AM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] A question on Relationships
>
> Lets see if I get this right...
> When I make a relationship between tables, I should bound the primary field on
> the one side with the foreign key on the many side, right? When I try to do
> this an set Referential Integrity, I get a message saying that "Relationship
> must be on the same number of fields with the same data types". Now how would
> this be posible if the primary key on the one side of the relationship is the
> auto number and the foreign key on the many side is a text field? Am I doing
> something wrong?
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
Tidak ada komentar:
Posting Komentar