Problems:
- The sub forms updates sporadically. when they don’t update the subforms shows empty subform datasheets, but when looking at the table the records are there.
- All the fields in the subform datasheets changes shape to “deleted” quit frequently when I move the mouse or click on an item outside the sub, aswell as switching between the tables.
-The app has been tested both with split and unsplit DB, working somewhat better when unsplit.
Short form desription:
-Choose Organizationcbo (Mainform): the value from this cbo is copied to a “hidden” txt, (txtOrg).
-The tab contains to pages (Notsubmitted, submitted), containing one unbound empty sub each, NotSub and YesSub
-When loading the form and when ever the ok button is pressed, the source objects of these subs are set to sub NotYb and sub YesXb, the choice of source objects depends on what quarter we are in.
-The NotSubmitted page sub should show an equal number of records to the NrOfResourcesTxt (13 in the example above)
-These subs are forms with a query each as record source, with org = txtOrg as a critera, dividing the same org records of table shadowRecordstbl between them.
formstructure:
cboOrg/cmdOK(Mainform) ->Tag(MainForm) -> NoSub/YesSub(TagSubforms) -> NotYb/YesYb(subform source objects) -> queryNb/queryYb(record source for the NotYb/Yesb datasheetforms) -> shadowRecordstbl(from which queryNb/Yb selects their records.
A short description of the process when pressing OK:
1. The Orgcbo.column is used as critera for the queries aswell as for determining other info displayed on the form.
2. I us an ADODB connection to delete former shadowRecordstbl records and to add them again, thus only having the current org records in the tbl.
3. I use an ADODB connection and recordssets to add records to the shadowRecordstbl.
4. By declaring “Me!NotSub.SourceObject = "NotYb" I set the source object of NoSub, vice versa with the YesSub.
5. Then I repaint, requery and refresh, have tried them all, making little impact to situation.
6. finished!
Patterns:
In the test mode I now run it I have 3 orgs, the first one in the list has 103 records, the second has 56 and the third has 13.
There is no exact pattern, a very strong trend though:
Org1: errs extremely seldom when DB is unsplit, occasionally when DB is split.
Org2: errs occastionally when DB unsplit, often when DB is split
Org3. errs far more often than Org2&Org3 together in unsplit mode, very often when DB is split
I Have tried…
As mentioned before, forcing double&triple clicks on the ok helps at times. It seems to enhance the sensitivity the chance of the “delete” problem to occur. Manually “double clicking” by clicking again has a higher frequency of success.
I have had this problem for quit some time no, discussed it with guys who I used to treat as true Gurus, but one after the other have they lost their Halos…
Ideas….
Maybe update conflict/timing error caused by my use of he ADODB connection?
- The sub forms updates sporadically. when they don’t update the subforms shows empty subform datasheets, but when looking at the table the records are there.
- All the fields in the subform datasheets changes shape to “deleted” quit frequently when I move the mouse or click on an item outside the sub, aswell as switching between the tables.
-The app has been tested both with split and unsplit DB, working somewhat better when unsplit.
Short form desription:
-Choose Organizationcbo (Mainform): the value from this cbo is copied to a “hidden” txt, (txtOrg).
-The tab contains to pages (Notsubmitted, submitted), containing one unbound empty sub each, NotSub and YesSub
-When loading the form and when ever the ok button is pressed, the source objects of these subs are set to sub NotYb and sub YesXb, the choice of source objects depends on what quarter we are in.
-The NotSubmitted page sub should show an equal number of records to the NrOfResourcesTxt (13 in the example above)
-These subs are forms with a query each as record source, with org = txtOrg as a critera, dividing the same org records of table shadowRecordstbl between them.
formstructure:
cboOrg/cmdOK(Mainform) ->Tag(MainForm) -> NoSub/YesSub(TagSubforms) -> NotYb/YesYb(subform source objects) -> queryNb/queryYb(record source for the NotYb/Yesb datasheetforms) -> shadowRecordstbl(from which queryNb/Yb selects their records.
A short description of the process when pressing OK:
1. The Orgcbo.column is used as critera for the queries aswell as for determining other info displayed on the form.
2. I us an ADODB connection to delete former shadowRecordstbl records and to add them again, thus only having the current org records in the tbl.
3. I use an ADODB connection and recordssets to add records to the shadowRecordstbl.
4. By declaring “Me!NotSub.SourceObject = "NotYb" I set the source object of NoSub, vice versa with the YesSub.
5. Then I repaint, requery and refresh, have tried them all, making little impact to situation.
6. finished!
Patterns:
In the test mode I now run it I have 3 orgs, the first one in the list has 103 records, the second has 56 and the third has 13.
There is no exact pattern, a very strong trend though:
Org1: errs extremely seldom when DB is unsplit, occasionally when DB is split.
Org2: errs occastionally when DB unsplit, often when DB is split
Org3. errs far more often than Org2&Org3 together in unsplit mode, very often when DB is split
I Have tried…
As mentioned before, forcing double&triple clicks on the ok helps at times. It seems to enhance the sensitivity the chance of the “delete” problem to occur. Manually “double clicking” by clicking again has a higher frequency of success.
I have had this problem for quit some time no, discussed it with guys who I used to treat as true Gurus, but one after the other have they lost their Halos…
Ideas….
Maybe update conflict/timing error caused by my use of he ADODB connection?
Last edited:
