It could be in your Edit Loop.
Are you using .Update after after every edit?
It sounds like you are opening to much memory while executing your Edit code. That might be stating the obvious here. Look for closing down as many open methods as you can after each edit and update.
Yeah, that didn't solve the issue. Its all good having the code, but if VBA is not going to recognise the FileDialog data member its not going to run.
Libraries people !!! Are people using this function with the "microsoft office 11.0 object library"
I have aslo loaded
"Microsoft Scripting...
Too many recordsets been created??
Too many temporary tables been created ??
But to do it in under 60sec is pretty fast. Do you have some redundant loops in your code. I have worked with large DB's (large for Access anyway), 2-3mil records and haven't come across that sort of "bloating" in...
Yep. Excatly that.
But having declared the variable or not is not too important as to whether the method of DialogBox should show
up as a member of "Application" once the library has beeen referenced.
If you type in (it would not run but you can still do it)
Application.
And if the correct...
Hi.
I've used this before but at another job. I cannot find the reference library that allows me to reference the Filedialog method. I have loaded reference library "microsoft office 11.0 object library" which allows me to decalre a variable as FileDialog. But in the code
'My code
Set...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.