Jason,
First of all, I agree that a macro is the appropriate approach for running
via scheduler.
What is happening here is very unusual. Sorry it is causing you such grief.
It is not the fault of macros per se, as demonstrated by the fact that it
works on another PC. This indicates that there is "something" weird going
on with your computer, which I can't imagine what that would be. However, a
complete un-install and re-install of Office would be my next step.
--
Steve Schapel, Microsoft Access MVP
"JK" <jasonk at necoffeeco dot com> wrote in message
news

19194E0-66F0-4D7B-ABD9-(E-Mail Removed)...
> I still am unable to copy/import a macro without the macro data being
> blown
> away. I did try it on another PC within our company network and it worked
> fine. I have no reason to believe my PC or my Access App. is corrupt.
>
> When began developing the application I'm working on now - I was a major
> rookie. I used a lot of macros to open forms and reports. The application
> is
> so big at this point it would take a while to track every macro down to
> convert to VBA.
>
> And there is still the problem of the one macro that I run using the
> Windows
> Scheduler. I don't know how (if possible at all) to run a VBA sub using
> the
> windows scheduler. Maybe I'll post that question and begin converting all
> macros to VBA and just never use a macro in my Access Apps. again.
>
> I appreciate your help.
>
> Jason