G
Guest
This has to be easier to do than what I am expeiencing. Hope someone finds
this interesting enough to look into.
I have only 1 table with fields:
ID, A_1, A_2, A_3, ... A_n where ID is the PrimaryKey
now I want 2 forms.
Form_1 should contain the fields ID, A_1, and A_2 only in a tabular
construct for this is an abbreviated view of some otherwise verbose info in
A_3 thru A_n.
Form_2 should contain ALL fields in a Justified layout with SingleForm view
enabled
Form_1 should support sorting in the Click_Event for each of the 3 column
headers.
Now when Form_1 is opened, I want the user to be able to filter or sort on
any column.
So far so simple right.
Now, when the user Double Clicks any field on a record in Form_1, I would
like Form_2 to open and GoTo the corresponding record. Likewise, the
underlying datasource for Form_2 should be Filtered and Sorted according to
the current state of Form_1 so that cycling thru, the records would appear in
the exact same order as shown in Form_1's current layout.
If anyone has an example of this it would be a HUGE help to me.
The problem I am experiencing is that when the user closes Form_2 and
returns to Form_1 that remained open for the duration, and tries to apply a
2nd filter, the filter is ignored if a column sort was applied the first time
around.
If any one has read this far and wants more clarification to dig into this
seriously, I can provide my project and DB for u to take shot at it. This is
actually an access project with a SQL Server backend. hehehe ... and the
filters are actually ServerFilters ... when the OrderBy in the column header
click_event is omitted everything works fine... Form_1.ServerFilter and
Form_1.Current(record number) are passed from Form_1 to Form_2 in the
field_Double_Click_Event. Form_2 obeys the filter and goes to the appropriate
record. When a column sort is applied in Form_1 and Form_1.OrderBy is passed
to Form_2, subsequent attempts to filter on Form_1 do absolutely nothing.
That is, they return the previous recordset according to the previous filter.
Inspecting the Form_1.ServerFilter property shows that it did change to the
newest filter request, but the recordset is WRONG!
Good Luck with this one!
this interesting enough to look into.
I have only 1 table with fields:
ID, A_1, A_2, A_3, ... A_n where ID is the PrimaryKey
now I want 2 forms.
Form_1 should contain the fields ID, A_1, and A_2 only in a tabular
construct for this is an abbreviated view of some otherwise verbose info in
A_3 thru A_n.
Form_2 should contain ALL fields in a Justified layout with SingleForm view
enabled
Form_1 should support sorting in the Click_Event for each of the 3 column
headers.
Now when Form_1 is opened, I want the user to be able to filter or sort on
any column.
So far so simple right.
Now, when the user Double Clicks any field on a record in Form_1, I would
like Form_2 to open and GoTo the corresponding record. Likewise, the
underlying datasource for Form_2 should be Filtered and Sorted according to
the current state of Form_1 so that cycling thru, the records would appear in
the exact same order as shown in Form_1's current layout.
If anyone has an example of this it would be a HUGE help to me.
The problem I am experiencing is that when the user closes Form_2 and
returns to Form_1 that remained open for the duration, and tries to apply a
2nd filter, the filter is ignored if a column sort was applied the first time
around.
If any one has read this far and wants more clarification to dig into this
seriously, I can provide my project and DB for u to take shot at it. This is
actually an access project with a SQL Server backend. hehehe ... and the
filters are actually ServerFilters ... when the OrderBy in the column header
click_event is omitted everything works fine... Form_1.ServerFilter and
Form_1.Current(record number) are passed from Form_1 to Form_2 in the
field_Double_Click_Event. Form_2 obeys the filter and goes to the appropriate
record. When a column sort is applied in Form_1 and Form_1.OrderBy is passed
to Form_2, subsequent attempts to filter on Form_1 do absolutely nothing.
That is, they return the previous recordset according to the previous filter.
Inspecting the Form_1.ServerFilter property shows that it did change to the
newest filter request, but the recordset is WRONG!
Good Luck with this one!