Hi Chris,
I am about 80% through a project which will be using DP and I am hoping after about 2 years of solid development that it will be a commercially viable product. PHP, MySQL is also a good thing to learn but many of the skills for one transform across to the skills for the other. The whole web database thing does mean you have to get exposure to a wide range of technologies to pull it all together no matter what the database technologies are. Brian _____ From: [email protected] [mailto:[email protected]] On Behalf Of Chris Pedersen Sent: Thursday, 4 June 2009 7:24 AM To: [email protected] Subject: Re: [Dataperf] New Version Now Officially Released Thanks Brian The thing that was puzzling was that it was working before I used the new version of DataPerfect. Regardless, I restored from a backup of DP, then switched to the new version of DP, reindexed, and it worked fine. Thanks for the time and attention to this post. ~ ~ ~ ~ ~ ~ ~ ~ ~ On other matters, I'm going on a cruise this weekend so I'm either bringing my MySQL web forms integration or your DPweb tutorial. Much more familiar with dp - so thats the comfort factor. Commercially viable probably the other way. _____ From: [email protected] To: [email protected] Date: Thu, 4 Jun 2009 06:44:12 +1000 Subject: Re: [Dataperf] New Version Now Officially Released Hi Chris, Are the fields for linking the same types and lengths. Are you using a Virtual Link or a Panel Link from the parent to the child? On the surface is sounds like there should be a Panel Link, but if you are using a Virtual Link you must select the fields or the RV'a containing the field values in the same order as in the t=selected index of the child panel. Personally unless it is essential I try to use a non-data loaded field as my link primary key in the parent, eg an incrementing number, and then have that same formatted link field (but non-incrementing and als non editable) in the child panel, and then set the Panel Link from the parent panel for Update Delete, to preserver referential integrity/ I presume that in your example "US1234" represents these as a string concatenation of the two separate fields??? If you use data loaded fields such as countrycode and workorder number you need to be careful about ensuring changes in one being cascaded to the other Cascade Update, otherwise you can easily orphan the child records. But my best guess for your problem is that the format of the fields in the parent is not compatible with the format as used in the index of the child. Regards Brian _____ From: [email protected] [mailto:[email protected]] On Behalf Of Chris Pedersen Sent: Thursday, 4 June 2009 4:05 AM To: [email protected] Subject: Re: [Dataperf] New Version Now Officially Released Am I doing something silly. Parent/Child relationship. Using a report with a virtual link. Key fields: Country Abbreviation; Work order number. (identical in parent and child). Want a report something like: US1234 Account 1 Account 2 Account 3 etc. where accounts are the child records. US1235 Acount 2 Account3 Acccount4 US1236 This report worked formerly but does no longer.. Now all I get is US1234 US1235 US1236. Have reindexed. No difference. Seems simple... _____ HotmailR has ever-growing storage! Don't worry about storage limits. Check <http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutori al_Storage_062009> it out. _____ HotmailR has ever-growing storage! Don't worry about storage limits. Check it out. <http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutori al_Storage_062009>
_______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
