Originally Posted by
Joe8915
...I know where the problem lay and I know why it’s happing. I have found a few fixes but for the life of me I just cannot do it.
Then perhaps you could give us a bit of a hint! You post an app with two dozen or more Objects and don't bother to tell what's actually going on, other than the single word 'Overflow?' How can we reproduce the problem? Which Object? What actions?
We'd like to help, that's why we're here, but we're not mind readers!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007