record pointer (?) conflict

[mark kubicki]

I have:
- a data entry from (1 record at a time), and on it
- command button opens a pop-up form
- the purpose of the pop-up is to allow the user to view other records in
the table for comparison/edit with the one that is being entered
- on the pop-up is a combo that allow the user to navigate thru the records
- the command that opens the pop-up is: DoCmd.OpenForm stDocName
- the commands that allow navigation thru the combo are:
strSearch = "[Type] = " & Chr$(34) & Me![Type] & Chr$(34)
Me.RecordsetClone.FindFirst strSearch
Me.Bookmark = Me.RecordsetClone.Bookmark

The PROBLEM (it seems) is that scrolling around thru the records on the
pop-up mucks around with some sort of pointer or bookmark. This becomes
evident when returning to the main form where GoTo First/Last, Next/Previous
Record commands will no longer take you to all of the records - The first
one(s) and/or last one(s) are no longer accessible thru this method of
navigation (i.e. GoTo First may only take you to record #2, and/or GoTo Last
may only take you to record #48 or #49 out of (50) -I think the limits may
be determined by how many records were navigated thru in the pop-up.


-so, I suspect, my whole approach may be wrong

thanks in advance,
mark

(the reason for needing to be able to "see" other records while entering
data in one is purely editorial -but clearly a desired tool)

 

[ruralguy via AccessMonster.com]

I find it hard to believe that a completely separate pop-up form that uses a
completely separate RecordSet from the 1st form would affect the record
pointer or controls of the 1st form. Is there any interaction between the
two form?

I have:
- a data entry from (1 record at a time), and on it
- command button opens a pop-up form
- the purpose of the pop-up is to allow the user to view other records in
the table for comparison/edit with the one that is being entered
- on the pop-up is a combo that allow the user to navigate thru the records
- the command that opens the pop-up is: DoCmd.OpenForm stDocName
- the commands that allow navigation thru the combo are:
strSearch = "[Type] = " & Chr$(34) & Me![Type] & Chr$(34)
Me.RecordsetClone.FindFirst strSearch
Me.Bookmark = Me.RecordsetClone.Bookmark

The PROBLEM (it seems) is that scrolling around thru the records on the
pop-up mucks around with some sort of pointer or bookmark. This becomes
evident when returning to the main form where GoTo First/Last, Next/Previous
Record commands will no longer take you to all of the records - The first
one(s) and/or last one(s) are no longer accessible thru this method of
navigation (i.e. GoTo First may only take you to record #2, and/or GoTo Last
may only take you to record #48 or #49 out of (50) -I think the limits may
be determined by how many records were navigated thru in the pop-up.

-so, I suspect, my whole approach may be wrong

thanks in advance,
mark

(the reason for needing to be able to "see" other records while entering
data in one is purely editorial -but clearly a desired tool)

 

[mark kubicki]

no interaction that I know of (with 1 exception: the data source the combo
that chooses the pop-up record is filtered to not include the record
currently showing on the main form...)
(are we certain that they are using separate record sets of the same
table?) -don't see why they wouldn't be, but maybe I've got something new to
learn about!

-m

I find it hard to believe that a completely separate pop-up form that uses
a
completely separate RecordSet from the 1st form would affect the record
pointer or controls of the 1st form. Is there any interaction between the
two form?

I have:
- a data entry from (1 record at a time), and on it
- command button opens a pop-up form
- the purpose of the pop-up is to allow the user to view other records in
the table for comparison/edit with the one that is being entered
- on the pop-up is a combo that allow the user to navigate thru the
records
- the command that opens the pop-up is: DoCmd.OpenForm stDocName
- the commands that allow navigation thru the combo are:
strSearch = "[Type] = " & Chr$(34) & Me![Type] & Chr$(34)
Me.RecordsetClone.FindFirst strSearch
Me.Bookmark = Me.RecordsetClone.Bookmark

The PROBLEM (it seems) is that scrolling around thru the records on the
pop-up mucks around with some sort of pointer or bookmark. This becomes
evident when returning to the main form where GoTo First/Last,
Next/Previous
Record commands will no longer take you to all of the records - The first
one(s) and/or last one(s) are no longer accessible thru this method of
navigation (i.e. GoTo First may only take you to record #2, and/or GoTo
Last
may only take you to record #48 or #49 out of (50) -I think the limits
may
be determined by how many records were navigated thru in the pop-up.

-so, I suspect, my whole approach may be wrong

thanks in advance,
mark

(the reason for needing to be able to "see" other records while entering
data in one is purely editorial -but clearly a desired tool)

 

[ruralguy via AccessMonster.com]

Are you using the standard Nav buttons on the 1st form? Do you have the Nav
buttons turned on on the pop up form?

no interaction that I know of (with 1 exception: the data source the combo
that chooses the pop-up record is filtered to not include the record
currently showing on the main form...)
(are we certain that they are using separate record sets of the same
table?) -don't see why they wouldn't be, but maybe I've got something new to
learn about!

-m

I find it hard to believe that a completely separate pop-up form that uses
a

[quoted text clipped - 34 lines]

 

[mark kubicki]

on the first form, all the navigation is thru command buttons
on the second, navigation is only possible thru the combo box

Nav buttons are turned off on both forms

-----------------------------------------------

Are you using the standard Nav buttons on the 1st form? Do you have the
Nav
buttons turned on on the pop up form?

no interaction that I know of (with 1 exception: the data source the combo
that chooses the pop-up record is filtered to not include the record
currently showing on the main form...)
(are we certain that they are using separate record sets of the same
table?) -don't see why they wouldn't be, but maybe I've got something new
to
learn about!

-m

I find it hard to believe that a completely separate pop-up form that
uses
a

[quoted text clipped - 34 lines]

(the reason for needing to be able to "see" other records while entering
data in one is purely editorial -but clearly a desired tool)

 

[Stefan Hoffmann]

hi Mark,

- the command that opens the pop-up is: DoCmd.OpenForm stDocName

Try WindowMode := acDialog.

mfG
--> stefan <--

 

[mark kubicki]

with a (quick) check -that seems to have done it (I hope)! thanks

 

[Stefan Hoffmann]

hi Mark,

with a (quick) check -that seems to have done it (I hope)! thanks

Without this WindowMode your code after DoCmd.OpenForm is executed while
your popup is displayed.

mfG
--> stefan <--

 

[mark kubicki]

oh (thanks)

hi Mark,


Without this WindowMode your code after DoCmd.OpenForm is executed while
your popup is displayed.


mfG
--> stefan <--