Ah, I see. Yes that is a way to do it. The problem is that it means hard-coding the link. I need to be able to dynamically create the link because I actually have multiple data.mdb files depending on the development environment that's being used. So what I need is a VB code solution.
I have separated my application logic (forms, VBA code, queries) from my data and am unable to open my form. The form is in file DbAppl.mdb and the table is in file DbData.mdb. Any ideas? Thanks.
Since it appears that a VBA String can hold more than 255 bytes, I assuming that a possible solution is to handle the "join" using VBA code instead of the Form's Parent/Child Link "wizard" or an SQL (which doesn't allow it either). I was hoping there was a simpler solution.
I don't understand your suggestion. Perhaps there's more to Aliases than I know. Access is inhibiting me from comparing Memo columns, how would renaming a column get the Link to work?
I have DB2 Explain results that I'm displaying in an MS Access Form (and subforms) so I can view all the necessary info that I need to determine if the access path is acceptable or not. If I need to manually change the stats and re-run the Explains then it's possible that the QueryNo could...
I have a form/subform that I want to link together using a memo column, yet when I try Access tells me that the column datatypes are incompatible. I've even tried making both the form's and subform's recordsource be the same table. Any idea how I can do this?
The user isn't choosing a field. The current record contains the data that the subform needs to use. I am not using parent/child links because that is much slower than changing the SQL to link the data. Apparently what Access does is to execute the query and then after it builds the results...
I've tried using form.requery in the form's OnOpen event yet it isn't executing the updated subform's query.
I'm only using * because in that case I actually am displaying all columns on the subform.
Because my tables were already large I split them up by environment to speed up data maintenence and retrieval. Thus I have table names which contain the environment as part of the table name (ex: tbl_TEST_MyTable, tbl_PROD_MyTable). Once the user sets the environment they want to use (by...