topic Loosely coupled problem in QlikView https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259411#M1208217 <HTML><HEAD></HEAD><BODY><P>Hello Bharethe,</P><P>Have you resolved this issue? I am also facing such kind of issue. If yes, let me know how you have resolved it. If not also hope we will work together to resolve the issue which we are facing.</P><P>Please do reply!</P><P></P></BODY></HTML> Wed, 30 Jun 2010 07:22:00 GMT 2010-06-30T07:22:00Z Loosely coupled problem https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259409#M1208215 <HTML><HEAD></HEAD><BODY><P>Hi all..</P><P>I have attached the document for the loosely coupled problem i have faced. Can anyone rsolve it.</P><P>thanks,</P><P>bharathe</P><P></P></BODY></HTML> Mon, 24 May 2010 11:23:17 GMT https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259409#M1208215 2010-05-24T11:23:17Z Loosely coupled problem https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259410#M1208216 <HTML><HEAD></HEAD><BODY><P>your problem is quite simple. there are 2 easy ways.</P><P>first- make use of qualify and unqualify, this will remove loops by attaching a prefix in the table.</P><P>or</P><P>second-make use of alias so that can rename a particular field.</P><P>my suggestion being that u should go for qualify and unqualify as it's more of a professional way of removing synthetic keys or loosely coupled loops in qlikview.</P></BODY></HTML> Thu, 10 Jun 2010 13:48:57 GMT https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259410#M1208216 2010-06-10T13:48:57Z Loosely coupled problem https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259411#M1208217 <HTML><HEAD></HEAD><BODY><P>Hello Bharethe,</P><P>Have you resolved this issue? I am also facing such kind of issue. If yes, let me know how you have resolved it. If not also hope we will work together to resolve the issue which we are facing.</P><P>Please do reply!</P><P></P></BODY></HTML> Wed, 30 Jun 2010 07:22:00 GMT https://community.qlik.com/t5/QlikView/Loosely-coupled-problem/m-p/259411#M1208217 2010-06-30T07:22:00Z