Re: SQL.IEM -324
Posted in 1998
Topics: SQL Development & Query Writing
Emmon, Your a Godsend! At least I got someone to respond. Thank you for now. For what it's worth, our version of OPENLINK is legal. Since I didn't 'feel' the error was a result of OPENLINK (but may be), I didn't call you folks. I appreciate whatever else you can add. Here are some answers to your questions. 1) sql.iem, yes, is an INFORMIX Error Message file. Its permissions are 644. As for being corrupt, I can't say. I can perform things like the UNIX 'strings' command on it as well as 'od -c'. 2) On the SCO box, when I enter in, 'finderr -324', I do get the ambiguous column error-description. EVERY column in my 2-table select stmt in ACCESS has the table-name qualifier. As I mentioned, absolutely NO code has changed in the last year and a half. Everything worked fine on BOTH PCs until that power failure. All boxes are up and running and not having any other problems. The 1 PC works intermittently between Access and INFORMIX on SCO, though it's slow. The 2nd PC only works on single table selects. 3) Forgive me, when asking, 'try a Pass-through query in Access', do you mean a plain, old query? Right now, stand-alone queries and queries in modules don't work on multiple-table joins. Only the single table selects. Please clarify if I'm not helping you on this point. 4) When asking, 'trying a manual link', I'm not sure what you mean? I can select data from the SCO box via ACCESS when doing single-table selects. Again, multiple table joins AND qualifying the columns with the table name gives me the same results. Emmon Simbo wrote: > Hi > > Thank you for using Openlink Software > > From what I understand, this power failure for some reason has stopped you > from being able to link more than two tables in Access. What happens when you > try to do a Pass-through query in Access with a join in the tables. The .iem > file as you may well know is the Informix error message file and has this flie > been corrupted in any way and what are the permissions on that file? > > With regards the error you are getting, it denotes an Ambiguous column name. > 'A column name shown appears in more than one table listed in the FROM clause > in the query. The database server needs to be told which of the columns to > use. When you link your tables, are they prefixed by a table name and > secondly, are you trying a manual link? > > Please let me know how you get on. > > Best Regards > > Emmon Simbo > Openlink Software