Hello,
I have discovered a bug in v7 that has been corrected in v8. It has to do with the
<Object>.duplicate_record() function. Sorry for the length of this, but I have detailed it.
The attached in an example. The database is for people CONTACTS. It has One main data table: CONTACTS and two Forms: F_ContactsMain and F_ContactsEntry. The original database built in ACT! has husband and wife together in one record with either the man or the woman, whoever was the primary contact, as the primary in the CONTACT table and a field "Salutaions" that has both spouses names. The new database in A5 will have each person separated into independant records. The user wants to go through each record
(there are hundreds) and make a few changes in each record, one change being the creation of a new record for the spouse of the person primary person in the CONTACT table.
The main Form: F_ContactsMain contains an embedded browse that displays all the table records. Stepping through the browse records, an OnFetch form event fires a script that probes the table for the presence of an existing spouse record. A yellow button with the text = MATE will 'show' if a spouse is present and 'hide' if a spouse record does not exist. This yellow button resides beneath the "Salutation" field that shows the names of the man and woman as it existed in the original ACT! database. I have created two scripts to enter the spouses into a new record,( Wife= pink button and man= blue button) one for man and one for wife. Upon viewing a 'salutation' with two people listed, and NO yellow button, which if present would indicate both spouses reside in the table, the user will be alerted to add the spouse to the database. Here is where the script that adds the spouse comes to play.
It does the following:
1. Captures the uniqueID (Friend_id) of the contact from the F_ContactsMain form.
2. Opens the F_ContactEntry form (based on the same table) and filters it the Friend_id.
3. >>>>> v7 ERROR FOCUS <<<< Duplicates the record using F_ContactEntry.duplicate_record(2).
4. Enters needed field values, commits record and closes F_ContactEntry form.
This works like a charm in v8, and errors out in v7 in step 3.
My angst/dismay is I am 98% complete with a v7 build that NEEDS this function to populate/establish the main table of this application for users already having purchased a v7 package to run this application. Arg!!!
Any thoughts knowing a bug report for a v7 issue falls on closed ears?
I have discovered a bug in v7 that has been corrected in v8. It has to do with the
<Object>.duplicate_record() function. Sorry for the length of this, but I have detailed it.
The attached in an example. The database is for people CONTACTS. It has One main data table: CONTACTS and two Forms: F_ContactsMain and F_ContactsEntry. The original database built in ACT! has husband and wife together in one record with either the man or the woman, whoever was the primary contact, as the primary in the CONTACT table and a field "Salutaions" that has both spouses names. The new database in A5 will have each person separated into independant records. The user wants to go through each record
(there are hundreds) and make a few changes in each record, one change being the creation of a new record for the spouse of the person primary person in the CONTACT table.
The main Form: F_ContactsMain contains an embedded browse that displays all the table records. Stepping through the browse records, an OnFetch form event fires a script that probes the table for the presence of an existing spouse record. A yellow button with the text = MATE will 'show' if a spouse is present and 'hide' if a spouse record does not exist. This yellow button resides beneath the "Salutation" field that shows the names of the man and woman as it existed in the original ACT! database. I have created two scripts to enter the spouses into a new record,( Wife= pink button and man= blue button) one for man and one for wife. Upon viewing a 'salutation' with two people listed, and NO yellow button, which if present would indicate both spouses reside in the table, the user will be alerted to add the spouse to the database. Here is where the script that adds the spouse comes to play.
It does the following:
1. Captures the uniqueID (Friend_id) of the contact from the F_ContactsMain form.
2. Opens the F_ContactEntry form (based on the same table) and filters it the Friend_id.
3. >>>>> v7 ERROR FOCUS <<<< Duplicates the record using F_ContactEntry.duplicate_record(2).
4. Enters needed field values, commits record and closes F_ContactEntry form.
This works like a charm in v8, and errors out in v7 in step 3.
My angst/dismay is I am 98% complete with a v7 build that NEEDS this function to populate/establish the main table of this application for users already having purchased a v7 package to run this application. Arg!!!
Any thoughts knowing a bug report for a v7 issue falls on closed ears?
Comment