Tom, I'm not sure I understand what you mean by "write to the form and have it change the table" - the form IS the table. Well, not really. It's SHOWING what's in the table. Bound fields on a form automatically are posted to the underlying recordsource if you change the displayed data and commit the change (record movement, form closure, explicit SAVE, etc).
Also, your reference to the first record and the use of the INDEX of the table seems confused. The index setting merely determines which of several possible indices your code will use for record navigation. It sounds like you might be opening the table and refencing the first record, but not doing anything to MOVE to subsequent records.
I think you're overcomplicating this process. Display your records on a form (single or continuous mode) and have a command button or whatever that runs your markup-language stripping routine for the current record:
Sub btnFixIT_click()
if Instr(me!configure, "<"

> 0 then
{ strip out the markup tags }
End if
end sub
If you wanted to do this procedurally, you'd do something like this in a sub or function:
-----------------------------------------
Sub FixEmAll()
dim rst as recordset
set rst = CurrentDB.OpenRecordset("Your table here"
With rst
while NOT .BOF
do
.moveNext
if Instr(!Configure, "<"

> 0
{ strip out markup tags )
end if
.Update
Loop
.Close
End With
set rst = Nothing
----------------------------------
That may not be the exact syntax but it should provide you with the idea of what it is you want to do.
BTW, there's no reason to worry about an index if you're navigating through every record in sequence.
HTH
There are two ways to argue with a woman - neither one works.
Another free Access forum:
More Access stuff at