Hi All,
We have a small VFP 8.0 synchonization utility that picks data from a VFP 8.0 database, converts it into XML and sends it over the net to an Oracle database. It has a timer control on it which makes sure that this utility sends the data from VFP 8.0 to Oracle every 45 mins.
It has always worked on all the setups till now, except one. We have not been able to figure why it does not work on that one. Any hints or directions to think in
Regds,
BABS
Timer Control not kicking in
Hot Topic
- label format with underline and bold in spots
- object execel, word with vfoxpro
- proper practice: Grids with my own classes.
- External Connect
- during compile got error
- function argument is invalid...
- stop “invalid input”
- FoxPro v9 vs Visual dBASE Plus 2.01 BDE 5.2.02
- making irregular shaped forms in VFP 9.0
- VFP9 printing issue with multiple detail bands and group subtotals and/or summary totals
Visual FoxPro
- form caption
- Docking PrintPreview toolbar and Making PreviewContainer Modal Window
- Converted VFP 3.0 Project
- is it possible to automate ACDC from visul foxpro
- Closing Cursors
- Blinking Vertical Line hard to see in a textbox
- Grid headers default mouse pointers etc...
- Menu Pad Name Errors VFP80 - VFP90
- HOW TO ADD AUTOMATICALLY A LOT OF .dbf FILE INTO A DATABASE .dbc FILE ???
- TreeView label edit.
Timer Control not kicking in
LealTing
Do you have error diagnostic code in place Do you have any logs that indicate each time it runs Do you launch the exe and it just runs forever with the timer firing off every 45 minutes Is there any chance the .Enabled gets set .F. or the Interval gets set to 0
Zoctan
By error log I mean for trapping/loggig runtime errors that might be causing this behavior. ie it can't open a file it needs.
I run code for days on end with a timer firing every few seconds where I then go out and poll other systems.
I think I'd actually suggest you go another route on this project. Why not convert the code to just run one shot and finish, and let the Windows Task Scheduler be the one responsible to kick off your exe every 45 minutes This way you don't the memory hogged up by the VFP runtime and your app 24/7.
Armanchos
Yes, we do have error log, but that only lets us know whether the data has been synced up completely. It also tells us when the synchronization has started and ended.
Yes, we start the exe and it keeps on forever during which it fires every 45 mins.
There is a chance that the interval gets set to 0, but we confirmed that its not happening.
Is there anything in the OS that can stop triggering the timer control or force it to turn off
Thanks,
BABS
chuotmay
it uses several megs of ram just sitting there, and VFP is bad about not releasing memory once it's gotten it allocated.
It's hard to say why one machine isn't working. It's one thing an error handler can help track down. Check http://fox.wikis.com for a few articles on the subject and some other links.
DreamState
I dont mind trying out ur suggestion, but
1. the exe hardly uses up any resources.
2. as I have said it works on 15 other setups, but not this one.
Anyway, I will try the Windows Task Scheduler.
BABS