 'Updates from 1.08.00 ->   .......
'----------------------------------------------------------
'Version : 1.08.00 (20/05/98)
'- Q409 : Took out the report generator and the report
'  launcher, and replaced them by calls to their external
'  equivalents.
'  Astrow makes temp.files astrlist.txt and
'  astrcurr.txt when you change the filter or the current
'  person. These files are necessary for the external
'  report generator and are deleted upon exit of astrow.
'- Q405 : Special weekly calculation will now subtract
'  weekly overtime from the daily overtime at the end of
'  the week (instead of regular).
'- Q391 : When something is changed in the curric yearly
'  holiday info, the next-year-days-taken are now correctly
'  calculated.
'- Q407 : Access bookings will not be put in the
'  communication queue anymore, they will be thrown away.
'- Q387 : The 'fieldname' field in the body-section of the
'  report generator has been made 30% bigger.
'- Q410 : The report launcher now contains 2 new buttons
'  to dump a report to file and to import a report from
'  file. This way, the dealer can make a report and send
'  only that one report to the customer.
'- Q411 : File generator now supports HHH.MM formats.
'- Q158 : Terminal group screen displays '*' before modified
'  terminals, as in the terminal location screen.
'- Q169 : Added quickbuttons to yearly overview to change
'  the topic.
'- Q408 : Fixed carryover problem.
'- Q234 : Curriculum fields can now be selected in the
'  file generator. For fields like nationality, sex, ...
'  use a numeric format to get the (internal) number and
'  alfanumeric format to get the name.
'- Q412 : After modifications for numerical sorting in the
'  filter, the paygroup/cyclus did not work anymore. This
'  happened because they were treated as numerical fields
'  -which they actually are- but displayed as alfanumerical
'  (the name is used, not the number stored in the curric).
'- Q319 : For new persons, the first booking/correction
'  will trigger calculations starting from the calc-start-
'  date instead of that date itself.
'- Q373 : Periodic analysis can display/print one extra
'  character; the format is now +hhhh:mm instead of +hhh:mm
'- Q201 : Configuration has 2 new parameters : no polling
'  start and end time. Between these two times, sleeping
'  mode and batch processing will be suspended, so all
'  files can be backed up. After the end time, the batches
'  that were scheduled in between will be executed.
'- Q413 : After giving terminal-timeout, a message
'  "communication not succeeded" will now be displayed
'- Q346 : There is one extra parameter in the configuration
'  screen : Translate files are windows format. Mark this
'  checkbox if you want to use a windows-based editor (like
'  notepad) to edit the translation files. This makes sure
'  that special characters, like  or  come out right.
'- Q414 : It is now possible to create one-line reports for
'  a certain period of time (not just one day). Put the
'  "don't print this column" parameter to 99 and all daily
'  lines, corrections and carry-overs will not be printed.
'  Curriculum items like name or personal number will also
'  be displayed in the totals line.
'- Q196 : It is now possible to put quotes (") around
'  fields in the file generator. Note that the quotes are
'  not included in the fieldsize (ie. field with size 32
'  will take up 34 spaces because of the 2 quotes)
'- Q415 : It is not necessary anymore to specify a field
'  size in the file generator. Putting 0 as fieldsize
'  will result in fields being exactly as big as the data
'  inside.
'- Q281 : The recalculation screen has one more date-option
'  to choose from : calculate x nr of months, where x can
'  be input.
'- Q416 : After adding a new DP and pushing OK, the added
'  DP will be show instead of the first DP in the list.
'- Q418 : LPT4 can now also be used to connect a dongle.
'- Q318 : There is a new option in the configuration screen
'  called 'skip double bookings from file/terminal'. Marking
'  this checkbox will cause Astrow to throw away double
'  bookings.
'- Q419 : When 2 users both added a person with the same
'  personal number, and pushed ok at the same time, that
'  person was stored in the database twice.
'- Q393 : There is one new calculation pattern : "Split
'  Weekly OT". This pattern works the same as weekly OT,
'  except for the following things :
'  Four new counters can be defined in the counter
'  definition : "SW Normalized abs.hours", "SW weekly bonus"
'  "SW Recup" and "SW OT". All are used exclusively for the
'  split weekly OT calculation.
'  -"SW Norm.Abs.Hrs" = The time item you have to define here
'   will NOT be filled up. It is only to indicate WHICH time
'   item is used. All absentees containing this time item
'   will not be added to the weekly bonus.
'  -"SW Weekly Bonus" = Same as weekly OT, except that some
'   absentees (see norm.abs.hrs) are not taken into account.
'  -"SW OT" = maximum of daily overtime and weekly bonus.
'   Will only be calculated on the last day of the week.
'  -"SW Recup" = maximum of daily overtime and weekly
'   overtime. Will only be calculated on the last day of
'   the week.
'  The carryover can be used in this pattern. Take note that
'  the balance is not used. Any balance influence has to be
'  achieved through the calculation routines.
'- Q420 : Landscape printing did not work on all systems.
'- Q421 : Bug in 4-4-5 weekly payperiod created strange
'  start/end dates for the period.
'
'- Translate xxSCRN.INI
'  [CONFIG], "85=Do not poll between :"
'  "38=Translation files are Windows format"
'  "39=Skip double bookings from terminal/file"
'  [FILEGEN], "30=Put quotes (") around fields."
'  [RECALC], "27=Months"
'  [COUNTERDEF], "67=SW Normalized Abs.Hours"
'  "68=SW Weekly Bonus", "69=SW Recup", "70=SW OT"
'----------------------------------------------------------
'Version : 1.08.01
'- Q    : Daily counters will be chopped off at their max/
'  min values. This will make sure that the periodic totals
'  correspond to the sum of the daily totals in case they
'  overflow.
'- Q    : Sleeping mode did not work when one of the
'  terminals was connected by modem.
'- Q    : The "days given" parameter in the annual holiday
'  maintentance screen was not correct.
'- Q    : The "employer" field did not work when used in
'  the filter.
'------
'version : 1.08.02

- Q435 : With version 1.08.01, the periodic analysis used the wrong format for the time items!

- Q436 : Payroll link gives 'syntax error' when you try to click the 'values' button in the counter definition part.

- Q437 : When starting out with a new (and empty) database   for reports, the focus was on the 'name' field.  You could start typing a name and input all parameters for that report.  When you then tried to store the report lay-out, all data were lost.  The focus is now on the 'add' button: before you can start typing anything, you have to click the 'add' button.

- Q447 : When you make a printout of the periodic analysis for the Time and Count items, the printout appears to be correct.  When you only printout a summary of count items, no values were printed.

- Q449 : In the bottom part of then report generator, it was not possible to use the shortcut <shift>+<F4> to delete a row.  An error message appears and the line was not deleted.

- Q450 : In the report generator, when the field '1st Abs Name' is chosen, the absentee is printed, but is not cleared on the following line.  The original absentee name appears on every day until another absentee appears. The calculation itself is ok, but the report was not reliable anymore.

- Q452 : The error message: replau, couldn't find object SELEKT * FROM pXX1998 where persnr=XX appears if you want to launch a report  if the periodic file is not build.(see report AD).

- Q445 :There is a problem with balance calculation.  This is reported by several customers.  The reports are always giving the correct balance (report = calculation), whereas the totals and the monthly overview show a different balance.  We have been able to isolate the problem to the carry-over value that gets wrong.  After a 'rebuild periodic totals', the proper value is restored.

- Q448 : There is a major problem in the recalculation of months.  For example BAL+ on the last day of the month is in minus and when you don't come to work on the first day of the next month, then the BAL+ should always be in minus.  This is not the case when you make clockings and don't do a daily calculation but a monthly recalculation or a calculation for a period in that month.  In the example we have a positive number for BAL+ on the first day of the next month.

- Q451 : With ASTROW in continuous polling mode, it seems that clockings for the nightshift are not automatically put together if autoshift is involved, at least not until after a recalculation.  It seems that other communication modes do not cause the same phenomenon.  Three sites in the UK have already reported the problem.  They can temporarily solve the problem by recalculating, but the system is not reliable any more.  A real solution has to be given.  A Belgian customer Lindpac suffers from a similar phenomenon.  There, the out-clocking on the last day of the month are not filed with the right people.  Instead they appear for people in the dayshift.  Problem also occurs when making a clocking correction in the daily overview.

- Q463 : A person has a balance of -21:00 on the very first day (printscreen 01/06/98).  On the report of that month(june) his Bal+ is correct (-00:09) for 01/06/98.  Then the screen and report are wrong for the next month (carry over): screen Bal+ is 08:00 and the report shows -21:01.  After rebuilding the periodic totals we get good results.

- Q468 : A clocking correction can be made on a day, resulting in an impossible situation when considering 2 consecutive days.  This situation is obviously resulting in an incorrect calculation of data.  When you recalculate the previous day (via daily overview) or you make a global recalculation (via 'Extras, Recalculation), the problem is rectified, resulting in new values being calculated.  This phenomenon can be easily simulated by adding the clockings as per enclosed report.  Note: insert the clockings on day 1, then calculate, then insert clockings for day 2.  This might be the clue to the Carron Phenix problem  (autoshift and polling mode, clockings for the nightshift are seperated instead of added to the same day, recalculation rectifies that.

- Q469 : Adding clockings to an 'open day' (no clockings yet, no anomalies, no absentees authorised) for the past month, results in a number of counters being calucated that weren't calculated before.  The daily overview visualises the correct status.  The 'body' part of the report picks up the appropriate value, the periodic analysis gives the correct value, but both the periodic totals and the 'bottom' part of the report are 'missing' the corrected value.  A recalculation does not solve this problem. 

- Q470 : When 2 paygroups are input in a person's curriculum, the report generator seems to pick up the carry over value as found in the second paygroup.  As such, the reports differ from the monthly overview on screen which is still correct! Ref. AD-Landesamt.

Version 1.08.03.

- Q445 : There is a problem with balance calculation.  This is reported by several customers.  The reports are always giving the correct balance (report = calculation), whereas the totals and the monthly overview show a different balance.  We have been able to isolate the problem to the carry-over value that gets wrong.  After a 'rebuild periodic totals', the proper value is restored.

- Q448 : There is a major problem in the recalculation of months.  For example BAL+ on the last day of the month is in minus and when you don't come to work on the first day of the next month, then the BAL+ should always be in minus.  This is not the case when you make clockings and don't do a daily calculation but a monthly recalculation or a calculation for a period in that month.  In the example we have a positive number for BAL+ on the first day of the next month.

- Q451 : With ASTROW in continuous polling mode, it seems that clockings for the nightshift are not automatically put together if autoshift is involved, at least not until after a recalculation.  It seems that other communication modes do not cause the same phenomenon.  Three sites in the UK have already reported the problem.  They can temporarily solve the problem by recalculating, but the system is not reliable any more.  A real solution has to be given.  A Belgian customer Lindpac suffers from a similar phenomenon.  There, the out-clocking on the last day of the month are not filed with the right people.  Instead they appear for people in the dayshift.  Problem also occurs when making a clocking correction in the daily overview.

- Q463 : A person has a balance of -21:00 on the very first day (printscreen 01/06/98).  On the report of that month(june) his Bal+ is correct (-00:09) for 01/06/98.  Then the screen and report are wrong for the next month (carry over): screen Bal+ is 08:00 and the report shows -21:01.  After rebuilding the periodic totals we get good results.

- Q468 : A clocking correction can be made on a day, resulting in an impossible situation when considering 2 consecutive days.  This situation is obviously resulting in an incorrect calculation of data.  When you recalculate the previous day (via daily overview) or you make a global recalculation (via 'Extras, Recalculation), the problem is rectified, resulting in new values being calculated.  This phenomenon can be easily simulated by adding the clockings as per enclosed report.  Note: insert the clockings on day 1, then calculate, then insert clockings for day 2.  This might be the clue to the Carron Phenix problem  (autoshift and polling mode, clockings for the nightshift are seperated instead of added to the same day, recalculation rectifies that.

- Q469 : Adding clockings to an 'open day' (no clockings yet, no anomalies, no absentees authorised) for the past month, results in a number of counters being calucated that weren't calculated before.  The daily overview visualises the correct status.  The 'body' part of the report picks up the appropriate value, the periodic analysis gives the correct value, but both the periodic totals and the 'bottom' part of the report are 'missing' the corrected value.  A recalculation does not solve this problem. 

- Q470 : When 2 paygroups are input in a person's curriculum, the report generator seems to pick up the carry over value as found in the second paygroup.  As such, the reports differ from the monthly overview on screen which is still correct! Ref. AD-Landesamt.

- Q422 : There have been some problems when the customer changes the absentee code definition after using it for some time.  This results in a lot of manipulations to rectify the problem.  It would be better to lock the absentee code definition once it has been input, similar to the filenumber in the curriculum.

- Q438 : It is not possible to get the name of departments in the reports: only the number is available.  As most actions (see curriculum, filter) are based on department names, it should be possible to use the named in reports.

- Q453 : You can't have the department name anymore in the reports in version 1.08.01

- Q454 : When you ask a report in version 1.08.01 from a person who hasn't clocked that week he has random figures in his overview. The cause is that this period hasn't been calculated. In the ASTROW version 1.07.06 he calculated first the period before he made the report. This must also be in this verson. (see also Q452)

- Q455 : With ASTROW version 1.08.01 you can have the message: 'invalid use of null'. 1) You have this error when you make an update from version 1.07.06 and if in the body defenition a field is empty (not the empty defenition but really empty)   2)When you have a new installation you can have the same error message by creating a new report.

- Q458 : There is a problem with sorting in reports.  Manual printing appears to work only when selecting name or badgenumber.  The reports printed automatically from the time-table, have similar problems.

- Q460 : When making a recalculation for a number of months that exceeds the number of months on your harddisk, then you get an 'illegal function call' error.  Astrow then aborts.  This should be properly checked!

- Q461 : We would like to see the default values for 'Number of months' open/on harddisk changed as the current settings give rise to problems.  We would like to see 36 months for both parameters.  This should avoid problems with the archiving function (doesn't work properly).

- Q462 : When you change the code  description of an absentee code, then this modification is not reflected in the daily or monthly detail.  Instead, you get an error at the next recalculation. (ASTROW 152=Daggrens werd verschoven door AutoDP.  Berekening O.K. Check fouten-logboek indien gewenst.).    In the logfile, you will then see the correct error: ASTROW 161 (Leesfout Afwezigheden Def.)?!  This has to be corrected.  Is it also possible to rectify the situation in the daily/monthly overview, or could there be a confirmation about the action the user is about to undertake?

- Q465 : The printout for the paygroup does not show the proper text for the carry over minimum.

- Q476 : When periodic flex is selected, a recalculation for 122 days or less is still ok, but if more than 122 days have to be covered, then ASTROW generates a 'subscript out of range' error.  When there is a technical problem with VB3, ASTROW should give a proper warning to the user.  Can be simulated by changing a person's paygroup from flex to periodic flex and then recalculate for several months.

Version 1.08.04.

- Q422 : There have been some problems when the customer changes the absentee code definition after using it for some time.  This results in a lot of manipulations to rectify the problem.  It would be better to lock the absentee code definition once it has been input, similar to the filenumber in the curriculum.

- Q432 :The WIBUKEY ini file is modified after installing an upgrade of 1.08.01  Apparently, the Serverfile is referring to the physical name of the harddisk where the wknet.dat is located, not the logical name.

- Q433 : It is not possible to use the 'browse' button in the setup to install ASTROW to the root of a network drive.  A double backslash is added (G:\\ASTROW).  It is also not possible to type in a path manually.  Long directory names are equally causing a problem.  This is causing too many problems.  As we have more and more customers installing to the network, this is become a serious problem.

- Q440 : When updating from a 1.07.06 version to the 1.08.01, the following errors occur: the wibukey ini file on the server loses the drive indication (c:\ASTROW becomes :\ASTROW); the replau and repbld ini files are not created when you run the setup_ws on the workstations.  This must be improved urgently as we cannot ship this version to the end-users.

- Q446 : When printing a report on a day where only 2 clockings were generated and those 2 clockings both happened to be within the core zone, the 1st clocking is not printed.  Instead a question mark '?' is printed.  Removing the core zone is a work-around, but the customer loses the possibility of checking on late arrival/early leave.

- Q453 : You can't have the department name anymore in the reports in version 1.08.01

- Q454 : When you ask a report in version 1.08.01 from a person who hasn't clocked that week he has random figures in his overview. The cause is that this period hasn't been calculated. In the ASTROW version 1.07.06 he calculated first the period before he made the report. This must also be in this verson. (see also Q452.

- Q458 : There is a problem with sorting in reports.  Manual printing appears to work only when selecting name or badgenumber.  The reports printed automatically from the time-table, have similar problems.

- Q459 : ASTROW has a problem in the treatment of annual holidays when the years overlap.  

- Q462 : When you change the code  description of an absentee code, then this modification is not reflected in the daily or monthly detail.  Instead, you get an error at the next recalculation. (ASTROW 152=Daggrens werd verschoven door AutoDP.  Berekening O.K. Check fouten-logboek indien gewenst.).    In the logfile, you will then see the correct error: ASTROW 161 (Leesfout Afwezigheden Def.)?!  This has to be corrected.

- Q465 : The printout for the paygroup does not show the proper text for the carry over minimum.  See printout.

- Q476 : When periodic flex is selected, a recalculation for 122 days or less is still ok, but if more than 122 days have to be covered, then ASTROW generates a 'subscript out of range' error.  When there is a technical problem with VB3, ASTROW should give a proper warning to the user.  Can be simulated by changing a person's paygroup from flex to periodic flex and then recalculate for several months.

- Q477 : Printing reports for more than 1 month is not supported by the report generator.  However, to make it possible to generate such reports without too many customer interventions, a new button has been added to make it available.

- Q478 : Holidays that have been scheduled and that are removed again at a later time, are removed from the holiday card list to the left, but not in the periodic totals.  A reconstruction of the holiday card solves the problem.  A fix has been implemented.

- Q480 : The monthoverview now always scrolls to its highest position to make it possible to see the full list in one window.

- Q481 : Password definition.Language database field: the software does not reflect the proper name field (1 and 2 are available).  This is confusion if both fields are used (multi-lingual environment).  This only happens in the filter module of the password definition.

- Q482 : Rebuilding Periodic Totals is now executed in order to overcome the problem of corrupt periodic data-files.  Various solutions are available, depending on the environment.

- Q484 : When you launch the reports the choice per default is previous week but the dates shown are the dates of today. You must first make an other choice before you can use previous week with the correct values.

- Q487 : In the annual holiday card, when you delete holidays that have been introduced in a future period with the following method :'absentee', 'use', 'delete all absentees with these specifications'. An error occurs in the holday card, the values in the totals have been adapted ( Days given, Days taken, Days left) but the detail lines concerning the deleted holidays are still to be found in the left panel. The rebuild of the holiday card from the begin of the year until a future date sets the situation right. At this moment, the client is obliged to rebuild the holiday card every day before he sends it to the terminal. This is not a good solution, because the rebuilding of the holiday card only works if all data has been saved. If the client can take his holidays from 01/01/98 until 01/04/98 and in the configuration of Astrow he only wants to keep 12 months, the rebuild of the annual holidays won't ever be able to solve the problem.

Version 1.08.05.

- Q496 : Out of stack space error occurs when browsing through the personnel list in the listbox on the menubar (happens since 1.08.0?, 1.08.01 worked well).  Astrow then aborts.

- Q492 : The new button in the report launcher to print reports covering multiple months, gives an error (Period 03/1999 does not exist.  Processing stops) when the next period (with reference to the current system date) has not been calculated yet.  The report should be able to activate that month (which happens when you plan absentees or special dayprograms..).  It is unacceptable to ask the customer to calculate manually.  On top of that, there is the loss of time when the report covers a lot of data/persons.

- Q488 : With a filter, the periodic analysis works if no options of corrections is being asked. If any of the 3 possibilities of adding corrections on first last or always is chosen the list that is being printed only shows the names of the persons within the filter.

- Q486 : Reports with the name and the field Current balance previous day , the value of the first person is being repeated for all the other person in the list.

- Q485 : The problem occurs for people who where absent from Thursday until Monday. No calculation has occurred has no clockings have been read. In the weekly reports, the Saturday and Sunday day-programs have been changed. On the paper it not the day-program of the cyclus that are printed but its the same day-program has the one used during the week. Not only is the day-program changed but also there are values in several counters for these two days. These values only show when a report is being printed. When a recalculation of the period is being asked, then all these problems disappear.

- Q466 : If you add a correction to the period totals, and the pay period crosses the calendar end-of-the-month, then the correction does not appear on clocking overview report.  It is fine if you apply normal pay periods.

- Q430 : The new calculation type for the Belgian market (SPLIT OT) does not seem to work properly when no weekly hours were achieved.  All other cases have been tested and confirmed to be working properly.  We have customers waiting for this calculation pattern.

- Q499 : When dragging absentees and inputting the 'from'-'to' date manually,an error message was generated.

- Q501 : The balance counter in the dailly overview waslimited to 9:59 as maximum value. This sometimes caused problems when manually adding more hours to the balance.

- Q502 : When the config.ini could not be found,a default config.ini was created. The default value for'# of months open' was then reset to 1 month,possibly resulting in data-loss.

- Q475 : Weekly pay-periods and flex carry-over is now supported.

- Q489 : Dailly OT and balance carry-over is now supported. The carry-over value is often used for recuperation of OT.

- Q493 : When all clockings are made in core-time,the reports did not properly show the first IN-clocking.Instead,the '?' appeared.

- Q497 : Inputting dates for reports can only be done in the fixed format dd-mm-yyyy! This will be visualised on the screen.

'-----------------------------------------------------------
'Version : 1.08.06
'- Q506: If you have more than 10 clockings a day in combination
'  with some absentee reasons you had an error message
'- Q505: Pay Periods defined to end before the end of the calender
'  month are not properly treated by ASTROW. If a pay period ends
'  e.g. on the 25th february, february is running from 26/02 to 25/3.
'- Q   : There was no carry over on the reports for a two weekly 
'  pay-period.
'- Q490: Clockings for the nightshift where clockings are normalised
'  to the previous day are initially stored in the database. When you
'  then mak a recalculation, the clockings on the 1th day of a new month 
'  disappear..... This only happens when there the In and Out Clocking
'  are generated on different pay-periods. When you are working in a 
'  polling mode the last clocking from the night shitft is not automaticaly
'  put to the previous day. (only after a recalculation).
'  (P.S. to solve this Q490 we had to rewrite this part in the source code,
'  because the polling mode module is a separete module)
'-------------------------------------------------------------
'Version : 1.08.07
'- Q516: While make a calculation in the future for the link.exe for 
'  night shifts the FBXXXX file is incorrect.
'- Q507: Holiday booked report. Error message period does not exist 
'  stops running for period in the future.
'- Q527: In some conditions the lines of the last clocking is repeated
'  on the next days
'- Q526: The value "current balance previous day" is always correct
'  within the month. But if the from date is the previous period the
'  balance is incorrect.
'- Q525: Lost of the clockings at the end of the month in some night shifts.
'- Q522: Re-process gives error in some conditions.
'- Q519: A person who hasn't clocked is not on the anomaly list in the printout
'- Q517: Periodic effective hours are correct in Astrow, but if you send them 
'  to the terminal => incorrect (value 0)
'- Q503: When using absentee codes with 2 digits => incorrect conversion 
'  to a 3 digit code.
'- Q518: Terminal and resultgroup couldn't be printed out anymore.
'- Q535: Nr of days <10 to keep in logging file was causing problems.
'--------------------------------------------------------------------
'Version : 1.08.08
'- Q548: Overprinting in the reports with payrol flex
'- Q550: Reports of a Belgian customers were empty if you remove periodic totals
'- Q538: Paid break is counting double in the night shift
'- Q534: 4-weekly pay-period: if the week end day is saturday then it creates a period
   for one week after the target date
'- Q532: Double clockings after problems with break defenition + poll.tmp not cleared
'- Q479: Adding an mc code for 1 hour regular hours. Adds to regular hours however
   if weekly overtime is used the 1 hour is not used in calculation and thus more
   than regular limit is reached.      
'- Q500: Stolen overtime together with Weekly viking is not working
'--------------------------------------------------------------------------------------
'Version : 1.08.09
'- Q549: A recalculation that start more than one month in the past gives error if you use two
'  different cyclus + paygroup.
'- Q539: In combination std start end + night shift => astrow calculates wrong.
'- Q554: Belgian legal system is working OK
'- Q541: If you have with the daily overview enough counters to produce a vertical scroll bar
'        this hides the minutes figures.
'- Q524: In 1.08.06 the balance in two weekly report is ok but you need a recalculation 
'        of the perioidc totals.
'- Q560: In the reports: the first line where the daily hours should be printed the 
'        prestation stays blank.
'- Q559: If the yearly holiday is used in hours, the first day of the holiday period is 00.00  hours
'- Q555: If you launch a report over more than 1 mo,th with the M+2 button the second
'        month stops at the end of the month and not on the asked date.
'- Q529: The holiday card is empty in some conditions. AFter rebuilding it's OK.
'- Q557: Autodp is not working if the first clocking is at 00.00 or 23.59
'-----------------------------------------------------------------------------------------
