Method:Classic General Q&A

Re: Failed at Context=138

Anonymous — Fri, 26 Jun 2009 20:51:44 GMT

Hey John,

Going by what you have explained, you have linked the RecordID from the Estimates table to the RecordID in the Customer table. This is where the error is since RecordID is required to have its own unique id. Remove the field that links these 2 screens and see what happens.

This should get you fixed up

Re: Failed at Context=138

jallen — Tue, 23 Jun 2009 22:51:52 GMT

I am now getting more information from Designer. "Failed at Context = 138. The master table (Estimate) cannot make a relationship to a child table (EstimateLine) becuase the tables are joined by a field (JobNo) that does not contain unique values." The JobNo is referrenced to the Customer table. I have attempted to change the JobNo to a unique field, but it will not save it.

By the way, (JobNo) is actually the RecordID.

Re: Failed at Context=138

Anonymous — Tue, 23 Jun 2009 15:17:28 GMT

Hey John,

What kind of report are you trying to make? What tables are you building the report off of? Once we get some information on what your trying to do, we can start working on it and give you some possible solutions. What is it your doing when you get this 138 message.

When trying to add a detailed table to your new table, are you selecting from the drop menu or are you typing it in manually?

Failed at Context=138

jallen — Mon, 22 Jun 2009 23:06:11 GMT

I am STILL not able to copy or create a new report in Disaster (Designer)! I have attempted to create a new report from multiple tables without success. There are some existing reports I can copy, but none from what I need - Estimates. I've loaded Disaster on multiple machines and I get the same error: Failed at Context = 138.

PLEASE HELP!!!!!