Very confusing issue
Here it goes. Trying to figure out why one table relationship works one way for a report link and another another table relationship doesn't. Tables we will look at: JOBS, SUB PAYROLL, ORDERS. Backg...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendAlthough you posted the JavaScript code, that is simply calling a code page. Typically you need a real developer to make changes to a code page. I suppose you could post the code page but it's probably unlikely that anyone on this forum will assist. You will probably have to contract with a Quickbase solution provider to get help.
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------
Thanks, Mark.
This actual coincides with our previous discussion. Do you think this code has something to do with the reason that JOBS seem to connect automatically with SUB PAYROLL, but not ORDERS? I can't seem to identify the field that "adds" the job to SUB PAYROLL automatically. I have to manually click "add order" to "connect" to JOBS
Also, there is no RECORD# field in JOBS. Only a TASK ID# (key field).
The KEY FIELDs in both SUB PAYROLL and ORDERS is the RECORD ID#
------------------------------
BuildPro
------------------------------
This actual coincides with our previous discussion. Do you think this code has something to do with the reason that JOBS seem to connect automatically with SUB PAYROLL, but not ORDERS? I can't seem to identify the field that "adds" the job to SUB PAYROLL automatically. I have to manually click "add order" to "connect" to JOBS
Also, there is no RECORD# field in JOBS. Only a TASK ID# (key field).
The KEY FIELDs in both SUB PAYROLL and ORDERS is the RECORD ID#
------------------------------
BuildPro
------------------------------