Well it's time for me to move on. thanks all

[George Hester]

I had this project working. I was able to workaround all the bugs and compensate for those things that aren't bugs but it looks like Access in code anyway is just not cut out for what I had in mind. The loss of array dimensions was bad but I thought I had that licked. I did but that wasn't enough. The stick that has broken the camel's back is this: the 3260 error. It has come back. I would need to run the code in a matter of seconds every few seconds. On average at least 30 times all pending. But all it takes is one 3260 error and my entire Linked Table is destroyed. I tried saving the Table using FileSystemObject at the very start of the code. But it don't matter. It will get destroyed when a 3260 arises. And it does on average of 5 or 6 continuous applications of this code. That isn't right. And if it was my code that was barfed then it ought to barf everytime. And that is not the case. It happily does what it is supposed to do for 5 or 6 repeated operations. Then it 3260 barfs and that's the end of the Linked Table.

Granted this is all done in an Office XP application not Access. Outlook 2002 to be exact. Maybe its just a limitation of VBA. And in that case I'll have to get back to business with learning COM+. But I'm getting tired of the on again off again errors and I am sure ya'll have had enough of me. Well I think it's XML database time. If I can't get this in another fashion (I can run it manually (in the intermediate window) that works all the time) I just want to thank everyone that gave me some pointers alomg the way here. Much obliged.

 

[joseph]

"George Hester" <[email protected]>
??????:[email protected]...
I had this project working. I was able to workaround all the bugs and
compensate for those things that aren't bugs but it looks like Access in
code anyway is just not cut out for what I had in mind. The loss of array
dimensions was bad but I thought I had that licked. I did but that wasn't
enough. The stick that has broken the camel's back is this: the 3260 error.
It has come back. I would need to run the code in a matter of seconds every
few seconds. On average at least 30 times all pending. But all it takes is
one 3260 error and my entire Linked Table is destroyed. I tried saving the
Table using FileSystemObject at the very start of the code. But it don't
matter. It will get destroyed when a 3260 arises. And it does on average
of 5 or 6 continuous applications of this code. That isn't right. And if
it was my code that was barfed then it ought to barf everytime. And that is
not the case. It happily does what it is supposed to do for 5 or 6 repeated
operations. Then it 3260 barfs and that's the end of the Linked Table.

Granted this is all done in an Office XP application not Access. Outlook
2002 to be exact. Maybe its just a limitation of VBA. And in that case
I'll have to get back to business with learning COM+. But I'm getting tired
of the on again off again errors and I am sure ya'll have had enough of me.
Well I think it's XML database time. If I can't get this in another fashion
(I can run it manually (in the intermediate window) that works all the time)
I just want to thank everyone that gave me some pointers alomg the way here.
Much obliged.