Converting scripts to stand alone executable

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

Post Reply
Dave1142
Newbie
Posts: 6
Joined: Wed Dec 19, 2012 6:21 pm

Converting scripts to stand alone executable

Post by Dave1142 » Wed Dec 19, 2012 6:48 pm

I had created a number of scripts that figured out the most probable numbers to come up in the lottery. Most of the scrips just do things that MS Excel could not easily do. So the whole thing has to be re-written more or less as a stand alone program. Most of you might say just use C or vb for that, however the reason to use Macroscheduler is that it can more easily access new numbers when they come out, but on the down side is a little more combersome programming task. I am startiing out with pick 3 and will be looking at approximatley 220 numbers. Pick 4 will come later with 715 numbers. My question is does anyone think using an array within the script is a good idea or to do everything on a text file? I think text files would be messy way of doing things but a thought none the less. just looking for an opinion on the way I should be thinking about program structure using Macro Scheduler for this kind of application.

Dave

User avatar
PepsiHog
Automation Wizard
Posts: 517
Joined: Wed Apr 08, 2009 4:19 pm
Location: Florida

Hello

Post by PepsiHog » Wed Dec 26, 2012 3:56 am

Well, that depends. Are you going to want to store data? If you just want it to show you the numbers and quit, then there's no reason to write to a file.

I imagine you'd run this just before you go to play. And it sounds like you get your numbers from the web. So an array should be plenty.

But if you want to create an ever learning database then yes. By that I mean I think the data is so large that you could only hope to process so much before it becomes too long to wait for the data. If you wrote the data to a file you could have it not look at the data you already have, but get new data. Maybe indicate increases/decreases of percentages for data that was previously displayed.

Also, why text? It may be better to consider writting an ini file. Easier to add data to. And it's easier with MS to do this.

Create the file if it isn't already there
ifFileExists>path\file.ini
// do nothing
else
writeln>path\file.ini,res,[Play4]
endif

This creates your file. Then

editinifile>path\file.ini,

I won't spend time in details because I don't know if you've moved on. But if you decide to do the file thing, it's easy enough to get support.

PepsiHog
Windows 7

PepsiHog. Yep! I drink LOTS of Pepsi (still..in 2024) AND enjoy programming. (That's my little piece of heaven!)

The immensity of the scope of possibilities within Macro Scheduler pushes the user beyond just macros!

Post Reply
cron
Sign up to our newsletter for free automation tips, tricks & discounts