Madics
D-Verto Verison History
* New Feature
* Bug Fix
*
Amendments
Version 4.2.0.104
* If a floating point in the data file is
unable to be converted to a float value in the table we now just set this to zero,
before hand this was causing an errors for example if for some reason the
datafile had ]]]]]] instead of a floating point value.
Version 4.2.0.103
* Now checks to see if a Schedule Update
is running before it start another.
* Correct
an issue where the trigger file getting deleted after a Timed Shedule update
could of got stuck in a loop.
Version 4.2.0.102
* New
"Trigger Setting" of "Delete 'Trigger File' after 'Timed'
Scheduled Updates" if enabled DVerto will just delete the trigger file
off the server and ignore any of the records that were queued up that needed to
be updated, the theory of this is you have just done a full updated using the
'Schedule' over night so all the records are already updated and dont need to
apply any triggers that were possible that the overnight "Server/
* Update
log file when all records have been deleted and before the fresh starts. (If
Delete Records not Drop Table option is enabled).
Version 4.2.0.101
* Disable
trigger checks while Scheduled Updates are running, otherwise they started to
trip each other up.
Version 4.2.0.100
* New
"Trigger Setting" of "Reduced/Consolidated Trigger audit
logging" if enabled DVerto will not update its own log with every
record number updated/added/delete but just add a summary of how many
added/updated/deleted at the end of the process
Version 4.2.0.99
* Added
some error exceptions around setting the memo field, for example for blog field
types. (Madics Tech Specs etc)
Version 4.2.0.98
* The
Round imported values (to 5 decimal places) setting was not always being
invoked for all numeric fields.
Version 4.2.0.97
* Display
in the log if DVerto is unable to find/locate the .DAT (data file) and aborts.
Version 4.2.0.96
* Important - If you are using DVerto/
* New
"Trigger Setting" of "Sort trigger file in Table Order before
importing" if enabled DVerto will sort the
* Fixed an issues where DVerto failed to
read in a field type and returned with a "Failed, Error reading AMOS
records" invalid variant" message. This normally ocurred when
using the field LOOKUP via the Record Number.
* the DVerto log file is update to the
server every 1000 triggers instead of every 50 triggers.
Version 4.2.0.95
* Dates imported with a value of 999999 are
not coverted to blanks/null rather than erroring with a date conversion
error.
* .DVT files were not being used and included correctly in the
"Schedule/Batch" updates, only the DEF files were.
Version 4.2.0.94
* Added
two new 'Auditing' settings to the .DEF/.DVT configuration files to allow
auditing to be enable/disabled per file.
The new settings are:
AUDIT= If Y then file auditing is enable for
this file, even if its disabled in DVerto General Settings.
If N file auditing is
always diabled for this file, and again over rides the DVerto General Settings.
You can also update a different Audit
table rather than the default DVertoAudit table by setting the
following:
AUDITFILE={Audit table name}
Version 4.2.0.93
* New
DVerto Audit Table, If the following new setting is enabled "Update
DVerto Audit Table on changes" then DVerto will updated a table called
DVertoAudit with what Table, Record number & Time it was
changed/added. The Type field is Add, Update, Delete or Refresh (if the
whole tables was updated). The AudProcessed is not used with in DVerto
and can be used for external application to mark if the record has been
processed etc.
Version 4.2.0.92
* Added a new General Setting of "Delete
all records rather than table" if this option is enabled then the
tables on a full refresh are no longer dropped/deleted and completely
re-created but instead all records in the table are just deleted. The down side to this is its slightly slower
and if you change/add any new field the effect only takes place once the table
is manually deleted, the up side is you are able to create triggers etc on the
table as its no longer completely deleted.
Version 4.2.0.91
* Added a new Sybase Database
option in the Local Database/URL Connection settings. If enabled DVerto will
use SQL queries to get the Sybase tablenames rather than the ADO GetTableNames
commands.
Version 4.2.0.90
* A new dverto.cfg (based on the server)
can now to be used for additional setting if required in the future.
Version 4.2.0.89
* Added
a new General Import option of Round imported values if checked/enabled
all imported values will be rounded to a maximum of 5 decimal places rather
than its raw imported floating point value.
Version 4.2.0.88
* It
is now possible to get the trigger events to delete records from the table, to
enable this map a field in the .LAY file called DELETE_FLAG as a
binary or floating point. Then if the data file field value is set to zero the
record is then deleted out of the data table.
Version 4.2.0.87
* Reduce the Trigger'ed log file output
slighty.
* Update the log of the reason for a
Trigger "Full Update" - Table did not exist or Invoked by Server/
Version 4.2.0.86
* The server .DEF/.DVT/.LAY files are
first sync locally on the first trigger before any are read/actioned.
* Ignore any blank event lines in the
trigger file, previously this caused a "Trigger Event of not known,
ignored" in the log file.
Version 4.2.0.85
* If
a trigger event fails DVerto will stop and attempt to send an email with the
log file attached if the email address and SMTP server details are set in
Settings.
* Field/Import errors now include the
"field name" in the log file as well as the field number.
* Added
a 'Clear Log File' button in Settings/Log file.
Version 4.2.0.84
* Triggered
Updates now have the ability to execute a SQL Script once the updates have
completed, to enable this set TRIGGERQUERY= to the Madics SQL script name in
the releated {file}.DEF under the [SETTINGS], for example:
TRIGGERQUERY=INVMAS.SQL
* Triggers can also be disabled per a
file by adding DISABLE_TRIGGER=Y in the {file}.DEF
* There is a new LastUpdated field on all
DVerto tables this is updated with date/time the records was created/last
updated.
Version 4.2.0.83
* New -
Beta version of on on the fly record updates from the Madics Server, this can
be enabled under a new "Triggers" option in settings, first the
server trigger log file need to be set, for example:
\\{madics server
ip}\madics\miame\dsk0\001002\trig001.log
and then how many seconds to check the
server for update/changes, recommended setting this to about 60 seconds.
The Madics server will also need to be
enabled to create the triggers when the records are changed/Written this is
done in the OPR:MFHOOK.INI file as follows:
[FILES]
1=DSK43:INVMAS.DAT[241,17]
2=DSK43:SLCUST.DAT[221,17]
[SETTINGS]
DVERTO TRIGGERS=Y
Version 4.2.0.82
* DART/DVerto unicode support, Previous
it had issues with PC's installed with a Chinese character set.
Version 4.2.0.81
*
Added extra debugging around date/decryption on start up and if there is
an error update the error log rather than a pop up message.
Version 4.2.0.80
* When FTP is connecting to the server we
now check to see if its still connected for some reason and discount first,
before continuing.
Version 4.2.0.79
* The DVerto file definition file can now also
be a .DVT file (as well or instead of a .DEF file) this may help
solve confusion if you already have files with a .DEF extension or also using
the DART.SBX CSV import where these also have a .DEF extension.
Version 4.2.0.78
* Added
new settings to the .DEF file to allow you to replace the 'Madics_RecNo' field
name with a different field name. To enable/change this add/set the following
RECNO FIELDNAME=Data_Recno to the related .DEF file. (Where data_Recno can be
what ever you wish)
* We now use and check the DART settings
for a valid install license key.
Version 4.2.0.77
* Cosmetic and wording changes in
settings.
Version 4.2.0.76
* Added Binary 4 field conversion
support. B,4.
Version 4.2.0.75
* The LAY file lookup (see 4.2.0.72) now
allows you to use the internal created "Madics_RecNo" field, this
being the AMOS data file record number, useful if you have two parallel data
files that need to be linked via the record number.
Version 4.2.0.74
* If the LAY file based Table/Field
LOOKUP fails we now updated the log file (once) the first time the error
occured (and not on every record).
Version 4.2.0.73
* The divide by decimal placing tag codes
(see version 4.2.0.37 notes) can now be a field value from the record its reading,
so for example instead of having the Base_Price divide by PRICE_DIV whats
stored in the DECIMAL.CFG as below:
80,Nett_Value,F,6,PRICE_DIV
we can instead for example use the
records currency code as each currency may divide by a different about depending
on the decimal placing., so to do this replace the value or decimal placing tag
with the field name with <> each side, so for example:
120,Currency_Code,S,3
80,Nett_Value,F,6,<Currency_Code>
** Please note the field used needs
to be read/set before this in the .LAY file. **
** Also remember to add all the
codes used to the DECIMAL.CFG or decimal code table. **
Version 4.2.0.72
Introduce a basic table lookup, this allows you to add fields from an
existing database table. For example you may want to include the Customer Name
field on the Sale_History_Table but the original source data file in
In the LAY File (Data file Structure
Definition File) first create a field and set the start data position as
'zero' the field will be just created in
the Table with no information/data, but then add the following new parameters
in columns 5,6,7,8,9.
Column 1 - 0 (Zero, we not taking any
data from the .DAT file)
Column 2 - Field Name
Column 3 - Data Type, (S or F)
Column 4 - Field length, (6 for floating
points)
Column 5 - LOOKUP (This tells DVerto we
will lookup another table)
Column 6 - Table name (An existing Table
on the SQL Server database)
Column 7 - The Tables Field name we are
retrieving/looking up.
Column 8 - The data field name in the LAY
file to use to perform the lookup.
Column 9 - The field name in the SQL
Server Table to link by.
For example a part of your LAY file may
look this:
44,HIS_Cust_Code,S,6
0,HIS_Cust_Name,S,35,LOOKUP,Customer_Table,CUS_NAME,HIS_Cust_Code,CUS_CUSTNO
This will create a field called
HIS_Cust_Name and will use the HIS_Cust_Code value to lookup the CUS_Name via
the CUS_Custno field on Customer_Table.
Version 4.2.0.71
* The
AMOS random data files header "in use" count no longer need to be as
floating point at byte 9, you are now able to set this with in the data files
.DEF file buy adding the following section and fields. (If these are not set
the floating point at byte 9 is used by default).
[HEADER]
INUSE TYPE=STRING
INUSE BYTE POS=3
INUSE BYTE LENGTH=10
or
[HEADER]
INUSE TYPE=FLOAT
INUSE BYTE POS=9
INUSE BYTE LENGTH=6
etc
Version 4.2.0.70
* Added Column field selection to the
"Event Log"
* The "Event Log" now always
starts in the center of the main screen.
Version 4.2.0.69
* If the filename set in the HEADER
RECORD section of a .DEF file was not found we then try the same folder as the
as the data file its updating from, this mostly appies to running DVerto under
Windows (not Unix) and saves you setting the full data file path in the Header
Record section and only the file name is required as under Unix.
Version 4.2.0.68
* More tweaks to the main front screen
form and button base on the resolutions.
Version 4.2.0.67
* Tweaks to the main front screen forms
button spacing.
Version 4.2.0.66
* Added
a new "Compact View" in Settings, if enable this removes the
Individual Updates, Execute SQL Scripts and Wweb Updates options from the main
front screen, these are normal not required on the day to day running as most
of the updates are ran via the Schedule/Batch Updates.
Version 4.2.0.65
* Added
a a new "DVerto Event Log" this shows the update status and
information about the Import, SQL, Uploads and DART table rebuilds.
* We now store the SQL and Web update
start/end times, update status and errors, the complete status and title is
also now stored on the AMOS data import log.
* New log files also FTP back to the
* DART Tables rebuild failed if the Table
was not there to start with to delete.
Version 4.2.0.64
* We now store the AMOS data start/end
import date/times allowing duration of import reporting etc.
* When in AMOS Data file append mode the DEF
file and field struture was not always read causing import errors for the
next import.
Version 4.2.0.63
* Added additional information to the log
file if for some reason we are unable to convert an AMOS data to SQL/Access
data, we now log the Record Number, Field No and name, the start and length of
the field, the error and the data its converting.
Version 4.2.0.62
* Added
a "Delete Table" option in the "Table Views" use at your
own risk, you will get two warnings before the table is deleted.
* We
no longer do a full refresh if there is an error on the previous
"append" update, to force a full fresh update delete the table from
the database.
* The field import error dialog no longer
shows and waits for the user to select ok if we are running a batch/schedule
update, instead the update grid/log is updated.
* the DVerto Log file is now renamed when
it reaches 1mb instead of 500k.
* Fix
a field creation "append" errors, caused in previous version 4.2.0.61
Version 4.2.0.61
* With
Data import “Record Append” mode we now read from the last record added based
on the previous update and go from there, before hand it always start from the
first record but did not actual do any updates to the table/database until it
reach the new records at the end, now skipping the previously imported records
(what could be hundreds of thousands) it will really super charge and speed up
any Append imports.
* The tables were not being deleted and
re-created under some Append Only Rules causing a possible duplication of
records.
Version 4.2.0.60
* The overnight schedule script (.SCH)
comment lines (via ! or ;) were being added to the Schedule Grid, these were
skipped and should not of effected any update but should also not be there.
Version 4.2.0.59
* Small amendments to how the SQL Query
launches from the Schedule, sometimes the SQL completes but never exits to
continue to the next phase, hopefully this will solve or point us in the
direction why.
Version 4.2.0.58
* Added additional log information when
DVerto is starting up and caching the Server script files, time to time DVerto
just halted before it really started the extra log information may help to
determine where and why. We have also rejigged a little of the code what could
also actually solve the problem, but we not 100% sure where it occurred to
start with, time will tell.
Version 4.2.0.57
* The update Batch Schedule no longer
stops if a Madics/
Version 4.2.0.56
* The "Server files cache update" now shows a progress bar
rather than flashing up the file names, this give you a small idea how long it
will take.
* Added additional log information when running the Schedule/batch
Updates.
Version 4.2.0.55
* New "DART Rebuild" option, if this is enabled in settings,
you are able to rebuild or schedule DVerto to rebuild the DART Work Tables,
this will allow you to recreate any large DART Chart and Views overnight, DART
version 4.2.0.125 or later is also required.
Version 4.2.0.54
* Fixed a big In Individual Updates where it gave a missing leading
message saying it could not find the .LAY file if the DEF file name prefix was
different to the LAY file prefix, it was not looking at the DEF file MAPFILE
paramater to get the actual LAY file to use.
Version 4.2.0.53
* Web
Upload SQL Queries were being run 6 times in a row as the results flag was not
being set (see Version 4.2.0.51) so it then tried it another 5 times thinking
it failed.
Version 4.2.0.52
* The
Schedule was returning with an Exception Error if there was more than 30 DEF
files in the folder to process.
* Individual Updates could cause a Run Time
Error when existing DVerto.
Version 4.2.0.51
* Web Uploads - Additional error trapping
and changes if a connection drops in the middle of a table upload, we now wait 2
minutes and try again up to 6 times, then move onto the next table if we can,
and repeat the process.
Version 4.2.0.50
* Fix
'Divide by zero' Import AMOS/Madics files when calculating the schedule/batch
process bar and there was zero or only one record to import.
* Added additional error haddling when reading/update from AMOS/Madics
data files, report the error, record and field and then move on to the next
update if it can.
* Schedule/Batch scrolls and moved focus to
the item updating as it goes along.
Version 4.2.0.49
* When running the Schedule/Batch update the "Connecting to
database" form now is part of the actual Schedule/Batch form to reduce the
form flashing up time over time on smaller updates.
* Added extra error message trapping when
DVerto fails to connection to the local or remote database.
Version 4.2.0.48
* Reduce the size
of the Schedule/Batch form, was oversized on monitors with 1024x768 resolution.
* No longer show
the working/busy form when running in Schedule/Batch mode.
* The Schedule/Batch
form is no longer set to show-on-top until the very end, before hand if there
was an error you may not of known or accessed the message as it was hidden by
the Schedule/Batch form.
Version 4.2.0.47
* Changes
to the Schedule/Batch update interface, these now all show in a table instead
of flashing up one after another.
* Icon/Button order has changed on the front DVerto Control Panel.
Version 4.2.0.46
* Added
DVerto Profiles, use DVertoProfile.exe to set-up multiple profiles.
* To launch a profile directly as a
shortcut and skip the profile chooser you can add the profile ID at the end of
the EXE, so for example: "C:\Program Files\Madics Systems
Ltd\DART\DVerto.exe" "profile2"
* You are now able to launch more than
one DVerto at a time, but would not recommend running multiple updates at the
same time.
Version 4.2.0.45
* In View Data
loading a complete table into the new
Express Quantum Data Grid took a long time if there was hundreds of
thousands of records as it automatically gave you the ability to group, filter,
sort the fields etc. This has been change and the data start of in the grid in
a 'simple' mode where all this is disabled but the grid/data is displayed far
quicker. A new "Advanced Data Grid" button has been added to allow
you toggle back to an Advanced data grid mode allowing all the group, filter,
sorting options again but on large tables this could take a minute to apply or
so.
Version 4.2.0.44
* View Data now uses a new Express
Quantum Data Grid components.
* Removed check for updates in Settings, this is now a separate program,
if its not on your DART menu it can be located in C:\Program files\Madics
Systems Ltd\DART\DARTupdate.exe.
Version 4.2.0.43
* Bug
fix, Binary to date field was not actually created on the database table.
Version 4.2.0.42
* New Convert_Binary3_To_Date type of 'd'
(Lowercase D) this will convert dates stored in binary 3 to a date field.
Version 4.2.0.41
* SQL
scripts that error using the DROP command are ignored and no error is displayed
on the screen and DVerto continues, the log file is only updated.
Version 4.2.0.40
* Added the following two new filter
option function of (equal to greater than) and (equal or less than) to the .LAY
filter, these are entered as > and <.
Version 4.2.0.39
* LOG and INI files transfered back to the
Madics Server are now named with the PC Name rather than the static dverto.log,
data.ini, this solves the problem of the files being overwritten in a multiuser
enviroment.
Version 4.2.0.38
* Check For DART/Dverto update now launches
DARTupdate.exe rather than the updatecenter directly.
Version 4.2.0.37
* Add divide by decimal placing tag
codes, this allows you to use a code name in the .LAY files instead of hard
coding the value the field needs to be divided by, so for example the LAY file
orginally looked as follows:
169,Base_Price,F,6,100
You now can have it as:
169,Base_Price,F,6,PRICE_DIV
Then in a new file called DECIMAL.CFG
held on the server along with the .DEF and .LAY files you define PRICE_DIV in
the following format {ID},{Code},{Divide Value}:
1,PRICE_DIV,100
If the decimal.cfg files does not exist
then you can manually set/see these in the DVerto Settings - > Decimal
Places.
Version 4.2.0.36
* Added an 'Import Info' option in Settings,
this shows details of the records imported, date/time last imported, errors
etc.
Version 4.2.0.35
* New Append Mode this will only
append new records to a table. To enable this add APPEND MODE=Y to the .DEF
file.
If any of the following rules apply then apend mode will revert back to
normal update mode, and drop the table and start a fresh.
> If the data file changes file size. (Eg get expanded/contracted)
> If there was import errors.
> The table did not exist in the database. (was manually dropped/deleted)
> Different amount of fields in the table since the previous update.
> If there was less records in the data file than there was in the
the previous update. (Signs of a purge/deletion)
* We now update a new data.ini with
the details of the data import including the file size, record, field and error
counts.
Version 4.2.0.34
* The query execution timeout has but
increased from 30 seconds to 3 minutes.
Version 4.2.0.33
* SQL Server System Views no longer show in
the View Data list.
Version 4.2.0.32
* If HEADER RECORD=NONE then the
complete data file is read.(Including any unused records, use the FILTER
function in the .DEF file remove these)
* The schedule .SCH files now can have
comments in them, start the line with a ! or a ;
Version 4.2.0.31
* Added new setting of 'Stop after failed
remote uploads' if checked and a remote database table upload fails to connect
them we stop and prompt the user, rather than skipping the table and
continuing.
Version 4.2.0.30
* Multiple
SQL Queries can now be placed in the .SQL files, each query has to start with
[SQL].
Version 4.2.0.29
On the schedule web upload we now check
we have connected to the Remote Database, if this fails we pause for 1 minute
and then re-try up to 10 more time (10 minutes) then abort the script/sql
update.
Version 4.2.0.28
* SQL Table upload/copy was using a field
type of 'counter' (what does not exist in SQL Severs, just Access) so this
field is now uploaded as an 'interger'
Version 4.2.0.27
* Schedule Window never closed it self and
was self open after each schedule, this now closes when its complete.
Version 4.2.0.26
* Running the Manual schedule sent an email
but the Auto Schedule (Eg Over night) never sent any. ops.
Version 4.2.0.25
* You are now able to automatically email
the DVerto.log at the end of a Schedule.
Version 4.2.0.24
* Remote Server type connection in setting
was not being saved correctly.
Version 4.2.0.23
* You are now able to execute SQL Command
on the Remote/Web Connection, this is done in a .UPL file.
Example TEST.UPL file as follows:
[SETTINGS]
TITLE=Example Web SQL
[SQL]
CREATE TABLE Test_Table
(My_Name
char(50),
My_Age float)
Version 4.2.0.22
* Now refresh screen/forms every 30
seconds, previously it could look as if DVerto hung while it was running a long
query or upload.
Version 4.2.0.21
* Add a connection to Database
Version 4.2.0.20
* Fix a Schedule display program when updating
data (Broken back in 4.2.0.18)
* Added error checking when reading
DataRecords with no or incorrect headers so the record count could not be read.
Version 4.2.0.19
* Madics data type X was casing an error,
this is now treated as a (S)tring if its left/used in a LAY file.
Version 4.2.0.18
* The File Import Structure file (.LAY)
is now displayed at the bottom in the 'Update Data' option.
Version 4.2.0.17
* The SQL Command is now displayed at the
bottom when viewing the SQL Scripts.
Version 4.2.0.16
* Added 'Open Access Database' (if used)
in 'View Data'.
Version 4.2.0.15
* Enhancement to the LAY File (Data file
Structure Definition File)
New autonumber datatype of 0,{field
name},A,{start number} this is Automatic running number starting from the
value set in the 4th field.
For Example:
0,My_Running_Number,A,500 will create a field in the table as ‘My_Running_Number’ with a running
number starting from 501 and upwards..
Version 4.2.0.14
* Added
Test Remote and Local SQL Server connections in Settings.
Version 4.2.0.13
* Access
MDB database compress was not working between updates causing the Database to
grow larger and larger.
Version 4.2.0.12
* .SQL
Commands where not getting picked up from UNIX Servers if there were no UPL
files.
Version 4.2.0.11
* Added
Log display in Settings saving the user having to hunt down the DVert.log on
the PC or Madics Server.
* Added a 'Working/in Progress' box for
Schedules and SQL commands, previously it could look as if DVerto had finished
or closed it self down between SQL Executions..
Version 4.2.0.10
* The
DVerto.log file was not transfered back to the Madics Server on Madics Windows
Server Platforms instead it caused a FTP error.
* Adjusted a few minor Schedule Forms
display issues.
Version 4.2.0.9
* Local (and Remote) Access MDB files are
now compress after updates.
Version 4.2.0.8
* Running the schedule manually now lists
all the tables, scripts that will run allowing the user to deselect any if they
want.
* Web upload script files are now .UPL
files not .WEB files.
Version 4.2.0.7
* Added 'Upload to Web' option, this
allows tables in the local Database to be copied to a different database, in
most cases this will be Remote Web Database.
* Added DVerto check for latest/update
option in Settings.
Version 4.2.0.6
* Text
* Each time DVerto is run or once a day
the Dverto.log file size is checked and renamed to DVerto.001 if it reaches
500kb and the log is started fresh.
* Schedule updates with the latest
scripts from the server before running.
Version 4.2.0.5
* Enhancement to the LAY File (Data file
Structure Definition File)
If you set the start data
position as 'zero' the field is just
created in the Table with no information/data from the datafile its assigned
to, you can default this field to a value by setting it in the 5th parameter.
For Example:
0,Created_Date,D,6,01/08/2009 will create a field on the table as
‘Created_Date’ with a value of 01/08/2009 in every record.
0,My_Name,S,30,Steve will create a field on the table as ‘My_Name’
with a value of Steve in every record.
0,My_Age,F,6,100 will create a field on
the table as ‘My_Age’ with a value of 100 in every record.
Version 4.2.0.4
* Added field format type 'N' this is
used for converting values stored in as String Field (AMOS Data File) to
Numbers (Values) in the SQL/MSB Database.
* The auto generated fields Unique_ID is
now 'DVerto_Unique_ID' and Recno is now 'Madics_RecNo'
Version 4.2.0.3
Front screen interface changed you
display buttons under each other and not across the screen.
Version 4.2.0.2
Added a HEADER RECORD= to the .DEF
files, this allows you to read a different data file to get the records in use,
useful for example where Madics ORDHD2.DAT parallel data file to ORDHDR.DAT
does not have a header record as it uses ORDHDR.DAT.
Version 4.2.0.1
ASCII text files linked to data records
can now be imported into MEMO fields on the database, for example Madics Tech
Spec files.
Version 4.2.0.0
Beta Release