J
John B
I have an access app that uses bound object frames to bind tables with
automation apps such as word, excel, etc. This procedure works quite well
except for one monumentally bad design issue with bound frames, namely the
underlying table is not updated until the automation app is closed. Eg if
the user is working with word and clicks the save btn, nothing happens. In
fact, if I do something like call Me.Refresh in the form containing the BOF,
the automation app is closed(and the underlying table is updated.) To get
around this problem, I have tried using the applications saveas method to
create a temp file and then using a different BOF in a different (hidden)
form, create an entry in a different table using the temp file as input.
After that I delete the temp file. This is a little ugly but it works for
Word and Visio. However it does not work for Excel because calling Saveas or
SaveCopyAs seems to change the context from the BOF to the temp file with the
result that an error occurs when Excel is closed saying that it is no longer
connected to its client. I am working in vba. If anyone has any ideas, I
would like to hear them. Am I correct in assuming that I cannot get at the
underlying interfaces in vba? Or is there some way to restore the context to
the BOF after doing the saveas(or savecopyas).
automation apps such as word, excel, etc. This procedure works quite well
except for one monumentally bad design issue with bound frames, namely the
underlying table is not updated until the automation app is closed. Eg if
the user is working with word and clicks the save btn, nothing happens. In
fact, if I do something like call Me.Refresh in the form containing the BOF,
the automation app is closed(and the underlying table is updated.) To get
around this problem, I have tried using the applications saveas method to
create a temp file and then using a different BOF in a different (hidden)
form, create an entry in a different table using the temp file as input.
After that I delete the temp file. This is a little ugly but it works for
Word and Visio. However it does not work for Excel because calling Saveas or
SaveCopyAs seems to change the context from the BOF to the temp file with the
result that an error occurs when Excel is closed saying that it is no longer
connected to its client. I am working in vba. If anyone has any ideas, I
would like to hear them. Am I correct in assuming that I cannot get at the
underlying interfaces in vba? Or is there some way to restore the context to
the BOF after doing the saveas(or savecopyas).