Re: Please comment my thoughts -- Need help with application for controlling Time attendance...
Re: Please comment my thoughts -- Need help with application for controlling Time attendance...
- Subject: Re: Please comment my thoughts -- Need help with application for controlling Time attendance...
- From: Michael Ghilissen <email@hidden>
- Date: Tue, 5 Jul 2005 03:51:19 -0400
Oi Bernardo, tudo bom?
It is a typical batch processing application and you will have to
handle all the many transactions, events and reports with AS. Or you
could use the MySQL database engine in conjunction with AS, which is
easy enough to implement (see cocoaSQL and JB Le Stang's SQL Osax).
Or you could use MySQL with PHP (HTML Interface) - this is the solution
I retained to manage my investment technical analysis using the daily
prices of the S&P 500's stocks (see Marc Liyanage's www.entropy.ch for
MySQL and PHP installation).
If you insist on pure and plain AS, given the relatively small volume
of transactions (yet 12,000 p.a. to manage!), I recommend weekly files
for the daily transactions (in, out of work), and special events
(absence - authorized or not- , holiday, sick day, credit,
penalty,...). Permanent information such as employees name and
function, overtime calculation parameters and all transactions codes
could be stored in tables (also external files) and loaded at run time.
Transactions files are filled out by the employees recording their
time. Events files and 'permanent' tables are managed by the office
manager.
It is better to keep the data at the lowest possible aggregate level
for integrity and further exploitation. Every week you sort and merge
the transactions and the special events files to produce the individual
employee weekly summary (for signature) and total for the firm. You
also keep an annual tab of the firm's weekly totals.
To retrieve data on demand or over periods not in sync with the
physical file organization (as in the number of weeks in a month) will
be rather complex to handle with AS.
In conclusion, AS could work nicely in a tight frame and scope of
operation. If you want to increase the level of sophistication or
flexibility of your application, or simply if the volume of
transactions increased, then you would need to contemplate a database
engine behind the Studio UI and functionalities, alternatively a PHP
interface.
Does it help you?
--
Michael Ghilissen
On Jul 5, 2005, at 12:02 AM, Bernardo Hoehl wrote:
Hi Folks,
I have my own small company, and have been trying to learn Applescript
for the past 18 months. I still need a lot of help...
My next project is to build an application to controll Time attendance
in my small company handling 12 employees, replacing a 15 year old
mechanical clock.
The application will be built in AppleScript Studio, please forgive me
for posting my topic here, but I trully believe that the help I need
has nothing to do really with a graphical interface... It is basic
project planning, string and time handling...
I might begin testing the app, clicking buttons on the interface, and
end up using a bar code on card to register the employee's attendance
finnally, but this is not really so important at this moment.
My concerns are involving how I should approach the basic
functionality of my app. How it records the data, handles it returning
to me values and reports.
The objective of my app is:
1) Register in a log file when my employee comes in the morning, goes
out for lunch, comes back from lunch and finally when leaves work,
going home.
2) Once a month (may be weekly) I will need to print the current
report and collect the employees signature, saying that he/she agrees
with the text recorded.
3) Once a month I will need to email my accountant a number of worked
hours for each of the 12 employees.
My thoughts:
My idea is to create a folder at ~/Library/Application
Support/NameOfMyAPP/ , and eventually place all text files there.
(logs)
I am not certain if I should record one big long log file and try to
get my data out it, once a month or build individual files for each
employee, or even folders for employees, with separate text files for
each day or week, or month. ---> Please comment....
One idea is to write lines such as these:
Employee Named John Smith entering work at morning at Tuesday, 05
July, 2005 08:07:17 AM
or
Employee Named John Smith leaving for lunch at Tuesday, 05 July, 2005
012:02:45 AM
Would you be so kind to comment my thoughts and how you would approach
the solution?
How would you extract the values for each employee/month etc..?
Thank you for kind attention reading this long email,
Bernardo Höhl
Rio de Janeiro - Brazil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden