SQL's "bigint" data type and linked table in Access

[rharding]

I have a SQL database which contains a table (TblA) with a field (Fld1) defined as "bigint". When the SQL table is linked to Access the design view of the linked table shows this field as a data type of "Text".

I have another linked table (TblB) with a field (Fld2) defined as "int". I need to join TblA to TblB using Fld1 and Fld2 as the join. This of course does not work. There is a data type mismatch error generated.

I do not have the option of changing the data type of Fld1 to int from bigint. I can change Fld2 from int to bigint. If I do this, of course, when the table is linked into Access the data type will show up as "Text".

Should I be concerned about how Access "defines" the data type of these fields? In other words, can I use these "Text" fields in Access without having to worry if the joins are working correctly or not?

[ADezii]

I have a SQL database which contains a table (TblA) with a field (Fld1) defined as "bigint". When the SQL table is linked to Access the design view of the linked table shows this field as a data type of "Text".

I have another linked table (TblB) with a field (Fld2) defined as "int". I need to join TblA to TblB using Fld1 and Fld2 as the join. This of course does not work. There is a data type mismatch error generated.

I do not have the option of changing the data type of Fld1 to int from bigint. I can change Fld2 from int to bigint. If I do this, of course, when the table is linked into Access the data type will show up as "Text".

Should I be concerned about how Access "defines" the data type of these fields? In other words, can I use these "Text" fields in Access without having to worry if the joins are working correctly or not?

Fields involved in Relationships must be of the same Data Types with the exception of the AutoNumber Field which can be linked to a Long Integer, and even this is not really an exception.