Problems importing file into Access 2019
- Thread starter namliam
- Start date
isladogs
MVP / VIP
- Local time
- Today, 15:12
- Joined
- Jan 14, 2017
- Messages
- 18,518
Well you could almost do that by
1. automatically closing it at a quiet moment of your choice e.g. Using a timer event to trigger Application.Quit
2. then immediately decompiling it as a scheduled task after which it would be back running normally.
But if that's not practical, you'll need to devise a different solution
1. automatically closing it at a quiet moment of your choice e.g. Using a timer event to trigger Application.Quit
2. then immediately decompiling it as a scheduled task after which it would be back running normally.
But if that's not practical, you'll need to devise a different solution
I have completely rewriten the procedures and had add some logic here and there to capture empty files, empty fields or conversions that appearently the importer could happily process for me while the manual import cant.
as a result the entire thing now runs in approx 33% of time it used to which means it now runs twice per minute
It has sime issues with bloating the front end that I need to look into but its only a dozen meg a day, takes a good time to hit the 2 gig limit having to C&R once a month is a great improvement over the previous situation.
Thanks all for the ideas suggestions and pushes in the right direction.
as a result the entire thing now runs in approx 33% of time it used to which means it now runs twice per minute
It has sime issues with bloating the front end that I need to look into but its only a dozen meg a day, takes a good time to hit the 2 gig limit having to C&R once a month is a great improvement over the previous situation.
Thanks all for the ideas suggestions and pushes in the right direction.
Similar threads
