TweakUI wont run on my server cos its asking for the 64 bit version ??.
I'd be interested to hear from anyone else who is successfully automating stuff on a remote windows server.
Search found 6 matches
- Fri Oct 02, 2009 11:40 pm
- Forum: Technical / Scripting
- Topic: Remote Windows Server Automation
- Replies: 4
- Views: 5592
- Tue Sep 29, 2009 10:06 pm
- Forum: Technical / Scripting
- Topic: Remote Windows Server Automation
- Replies: 4
- Views: 5592
- Tue Sep 29, 2009 9:24 pm
- Forum: Technical / Scripting
- Topic: Remote Windows Server Automation
- Replies: 4
- Views: 5592
Remote Windows Server Automation
I'm new to MS and have spent a lot of time looking around this forum for info and advice on automating tasks on a remote Windows Server. I'm looking for some advice on the best way of automating tasks on a server which is always on but I'm not usually logged onto. I've been trying to automate some s...
- Tue Aug 18, 2009 10:01 pm
- Forum: Technical / Scripting
- Topic: unreliable macro sometimes stops at waitwindowopen
- Replies: 2
- Views: 3506
unreliable macro sometimes stops at waitwindowopen
Hi, I'm new to the product and have created a couple of macros that automate the import of a csv file into MS Excel. Most of the time it seems to work fine but every now and again the macro stops at waitwindowopen>save as. RunProgram>D:\Program Files\Microsoft Office\Office12\EXCEL.EXE D:\FTPRoot\Lo...
- Sun Mar 01, 2009 5:40 pm
- Forum: Technical / Scripting
- Topic: Newbie issue
- Replies: 1
- Views: 2776
RTFM !
Sorted it ! - spent more time on the tips and tricks and getting started stuff.
It was timing issue and adding a wait fixed it.
It was timing issue and adding a wait fixed it.
- Sun Mar 01, 2009 1:23 pm
- Forum: Technical / Scripting
- Topic: Newbie issue
- Replies: 1
- Views: 2776
Newbie issue
Hi - I'm currently evaluating the product and I've hit a problem on my first script. I'm using MS Access and I'm getting an warning prompt from Access telling me there are some errors on the imported data which will be saved to a table called import_errors. There is an OK button on the error message...