#Error - Bookmark Invalid

  • Thread starter Thread starter Thomas Kroljic
  • Start date Start date
T

Thomas Kroljic

Over the last few months I've been receiving the #ERROR error in all my data
entry fields within a subform along with a message box stating that the
"Bookmark Invalid". This happens enough that it is not only a problem, but I
am becoming extremely embarassed that I can not resolve the problem.

I have a form (frmSales) that contains a subform (subOrderlst). Typical
header/detail type of form.

The subform as a field called OrderPrice in the Form Footer section that
summarizes one of the columns (=Sum([ExtentedPrice])).

On the main form I have a field called txt_subTotal_1 that references the
the value in OrderPrice field on the subform as follows:

(=IIf(IsNull(subOrderlst.Form!orderprice),[Txt_DC]+[txt_TuningCharge]+[txt_d
isposalcharge],subOrderlst.Form!orderprice+[Txt_DC]+[txt_TuningCharge]+[txt_
disposalcharge]))

What confuses me about receiving this #ERROR problem is when the user gets
this problem. The #ERROR shows up in all of the subform fields only after
the user completes the line item in the subform and then enters data in a
field on the main form.

It appears that the user is able to first add a new line item in the
subform. Then when the user moves to a field on the main form, either by
clicking into that field or by pressing the tab/enter key until the cursor
moves from the subform to the next field on the main form.

So, now we have the user sitting in the next available field on the main
form. A record in the subform was entered. Now the user enters a value in
the field on the main form and attempts to move to the next field by
pressing the enter key. This is when the #ERROR error shows up in all the
fields in the subform.

Any suggestions?

I'm using Access 2000 within a Terminal Services environment on a W2K
server.

Oh yea. What I do to get the user out of this is: first I clear the
"Bookmark Invalid" message box. Next I right click on the form so I can get
it into design mode. Once in design mode, I close the form and back
completely out of the Access session. I then go back into the frmSales form
and open up the appropriate record. Surprisingly, the detail record is
there. With all its proper data. This also confuses me.

Any suggestions would be welcomed.

Thank you,
Thomas j. Kroljic
 
Thomas, I don't use TS, so hopefully those who do will reply as well.

Suggestions:

1. The Bookmark error can indicate a corrupt index. Try a Compact and Repair
(Tools | Database Utilities) on the back end, and also on the front end if
you have tables there as well.

2. I'm assuming you have split this database so that everyone has an
individual copy of the front end. If not, that might be the cause of the
problem.

3. When any one calculated field fails to calculate, it can cause #Error in
the others as well. That makes it hard to track down.

4. One cause of #Error is that Access misunderstands the data type. I find
it helps to set the Format property of all calculated text boxes that are
intended to result in a number. Workaround: Set the Format to Currency or
General Number or whatever.

5. Another cause is names that are misassigned. To avoid this, uncheck the
boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

6. If your subform has no records and no new records can be added (e.g.
AllowAdditions is No, or its recorset is read only), the form's Detail
section goes completely blank. Referring to the non-existent control resuls
in #Error. Even if the control is not in the Detail section, results can be
unreliable. Workaround: Leave AllowAdditions as Yes, and block new records
by cancelling Form_BeforeInsert.

7. If you are using Conditional Formatting (especially on a calculated
field), it is very easy to end up with an endless loop where the
calculations keep retriggering. The status bar reads "Calculating..." and
you can get error results. Workaround: Consider disabling conditional
formatting during trouble-shooting.

8. If you are modifying the database with a later version of Access, you can
trigger errors. Decompile the database using the TS version, and compact
again.

9. In a normal network environment, we ensure all workstations have SP3 for
Access 2000 and SP8 for JET 4. Presumably on TS you need to check that the
server has these service packs.

10. Timing issue. This one I never did solve completely. It involved
multiple users (not TS) on Access 2000 with the back end on an NT4 server.
Symptoms included the #Error. Also, combos and list boxes loaded only the
first 30 or 50 or so items where 100 or 200 were expected. I suspect it was
a network issue, since I was not able to repro. the situation in any other
setting. Users were not running as local computer administrator, so I don't
know if it was permissions, or the amount of traffic on the network, or an
issue with NT, but something seemed to be timing out and generating the
#Error. Restarting the session would sometimes help.

HTH.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Thomas Kroljic said:
Over the last few months I've been receiving the #ERROR error in all my
data
entry fields within a subform along with a message box stating that the
"Bookmark Invalid". This happens enough that it is not only a problem, but
I
am becoming extremely embarassed that I can not resolve the problem.

I have a form (frmSales) that contains a subform (subOrderlst). Typical
header/detail type of form.

The subform as a field called OrderPrice in the Form Footer section that
summarizes one of the columns (=Sum([ExtentedPrice])).

On the main form I have a field called txt_subTotal_1 that references the
the value in OrderPrice field on the subform as follows:

(=IIf(IsNull(subOrderlst.Form!orderprice),[Txt_DC]+[txt_TuningCharge]+[txt_d
isposalcharge],subOrderlst.Form!orderprice+[Txt_DC]+[txt_TuningCharge]+[txt_
disposalcharge]))

What confuses me about receiving this #ERROR problem is when the user gets
this problem. The #ERROR shows up in all of the subform fields only after
the user completes the line item in the subform and then enters data in a
field on the main form.

It appears that the user is able to first add a new line item in the
subform. Then when the user moves to a field on the main form, either by
clicking into that field or by pressing the tab/enter key until the cursor
moves from the subform to the next field on the main form.

So, now we have the user sitting in the next available field on the main
form. A record in the subform was entered. Now the user enters a value in
the field on the main form and attempts to move to the next field by
pressing the enter key. This is when the #ERROR error shows up in all the
fields in the subform.

Any suggestions?

I'm using Access 2000 within a Terminal Services environment on a W2K
server.

Oh yea. What I do to get the user out of this is: first I clear the
"Bookmark Invalid" message box. Next I right click on the form so I can
get
it into design mode. Once in design mode, I close the form and back
completely out of the Access session. I then go back into the frmSales
form
and open up the appropriate record. Surprisingly, the detail record is
there. With all its proper data. This also confuses me.

Any suggestions would be welcomed.

Thank you,
Thomas j. Kroljic
Click to expand...
 
Allen,
Thanks for your quick response and helpful suggestions. I'll go through
each suggestion tomorrow and check them against my databases (FE and BE).
This error is a pain, but you gave me several good things to look at and
possible modify.

Thank you,
Thomas j. Kroljic

Allen Browne said:
Thomas, I don't use TS, so hopefully those who do will reply as well.

Suggestions:

1. The Bookmark error can indicate a corrupt index. Try a Compact and Repair
(Tools | Database Utilities) on the back end, and also on the front end if
you have tables there as well.

2. I'm assuming you have split this database so that everyone has an
individual copy of the front end. If not, that might be the cause of the
problem.

3. When any one calculated field fails to calculate, it can cause #Error in
the others as well. That makes it hard to track down.

4. One cause of #Error is that Access misunderstands the data type. I find
it helps to set the Format property of all calculated text boxes that are
intended to result in a number. Workaround: Set the Format to Currency or
General Number or whatever.

5. Another cause is names that are misassigned. To avoid this, uncheck the
boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

6. If your subform has no records and no new records can be added (e.g.
AllowAdditions is No, or its recorset is read only), the form's Detail
section goes completely blank. Referring to the non-existent control resuls
in #Error. Even if the control is not in the Detail section, results can be
unreliable. Workaround: Leave AllowAdditions as Yes, and block new records
by cancelling Form_BeforeInsert.

7. If you are using Conditional Formatting (especially on a calculated
field), it is very easy to end up with an endless loop where the
calculations keep retriggering. The status bar reads "Calculating..." and
you can get error results. Workaround: Consider disabling conditional
formatting during trouble-shooting.

8. If you are modifying the database with a later version of Access, you can
trigger errors. Decompile the database using the TS version, and compact
again.

9. In a normal network environment, we ensure all workstations have SP3 for
Access 2000 and SP8 for JET 4. Presumably on TS you need to check that the
server has these service packs.

10. Timing issue. This one I never did solve completely. It involved
multiple users (not TS) on Access 2000 with the back end on an NT4 server.
Symptoms included the #Error. Also, combos and list boxes loaded only the
first 30 or 50 or so items where 100 or 200 were expected. I suspect it was
a network issue, since I was not able to repro. the situation in any other
setting. Users were not running as local computer administrator, so I don't
know if it was permissions, or the amount of traffic on the network, or an
issue with NT, but something seemed to be timing out and generating the
#Error. Restarting the session would sometimes help.

HTH.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Thomas Kroljic said:
Over the last few months I've been receiving the #ERROR error in all my
data
entry fields within a subform along with a message box stating that the
"Bookmark Invalid". This happens enough that it is not only a problem, but
I
am becoming extremely embarassed that I can not resolve the problem.

I have a form (frmSales) that contains a subform (subOrderlst). Typical
header/detail type of form.

The subform as a field called OrderPrice in the Form Footer section that
summarizes one of the columns (=Sum([ExtentedPrice])).

On the main form I have a field called txt_subTotal_1 that references the
the value in OrderPrice field on the subform as follows:

(=IIf(IsNull(subOrderlst.Form!orderprice),[Txt_DC]+[txt_TuningCharge]+[txt_d
isposalcharge],subOrderlst.Form!orderprice+[Txt_DC]+[txt_TuningCharge]+[txt_
disposalcharge]))

What confuses me about receiving this #ERROR problem is when the user gets
this problem. The #ERROR shows up in all of the subform fields only after
the user completes the line item in the subform and then enters data in a
field on the main form.

It appears that the user is able to first add a new line item in the
subform. Then when the user moves to a field on the main form, either by
clicking into that field or by pressing the tab/enter key until the cursor
moves from the subform to the next field on the main form.

So, now we have the user sitting in the next available field on the main
form. A record in the subform was entered. Now the user enters a value in
the field on the main form and attempts to move to the next field by
pressing the enter key. This is when the #ERROR error shows up in all the
fields in the subform.

Any suggestions?

I'm using Access 2000 within a Terminal Services environment on a W2K
server.

Oh yea. What I do to get the user out of this is: first I clear the
"Bookmark Invalid" message box. Next I right click on the form so I can
get
it into design mode. Once in design mode, I close the form and back
completely out of the Access session. I then go back into the frmSales
form
and open up the appropriate record. Surprisingly, the detail record is
there. With all its proper data. This also confuses me.

Any suggestions would be welcomed.

Thank you,
Thomas j. Kroljic
Click to expand...
Click to expand...
 
Back
Top