Hi,
I'm absolutly stumped (and more than just a little frustrated) . I have 2 tables that are linked together with a one-to-many relationship. When I open query-builder, I can't see all the fields in the first table (including the linked one!), and when I bring in the second one they don't link automatically like they should!
If I open a query that already had the relationship in it (built before I encountered this problem), I get this error message:
Microsoft Access can't represent the join expression tblPlatform.ID = tblVETProjects.VET2Platform in Design View
* One or more of the fields may have been deleted or renamed
* The name of one or more fileds may be misspelled
* The join may use an operator that is not supported in design view
The linking Field isn't even on the field list for the table!!! I have this same setup in my Test dB and it works fine. I have a replica of this dB on another server, no problem. One of my coworkers doesn't have this problem with the same dB! If I go into the SQL design directly, it works fine, but on the way to the query builder it gives me that error message. I'm lost. Any help would be greatly appreciated!!!
I'm absolutly stumped (and more than just a little frustrated) . I have 2 tables that are linked together with a one-to-many relationship. When I open query-builder, I can't see all the fields in the first table (including the linked one!), and when I bring in the second one they don't link automatically like they should!
If I open a query that already had the relationship in it (built before I encountered this problem), I get this error message:
Microsoft Access can't represent the join expression tblPlatform.ID = tblVETProjects.VET2Platform in Design View
* One or more of the fields may have been deleted or renamed
* The name of one or more fileds may be misspelled
* The join may use an operator that is not supported in design view
The linking Field isn't even on the field list for the table!!! I have this same setup in my Test dB and it works fine. I have a replica of this dB on another server, no problem. One of my coworkers doesn't have this problem with the same dB! If I go into the SQL design directly, it works fine, but on the way to the query builder it gives me that error message. I'm lost. Any help would be greatly appreciated!!!
