I'm looking for some tips on how to export a mysql database into a .mdb file that is readable by Microsoft Access 2007+ (and editable too!). It needs to be a script that can run on a Linux server (maybe using PHP?).
I have since found out we're already using this product elsewhere: -access-to-mysql-pro.php?DB=1It's running under Wine on our server, although I don't think it supports the latest versions of Access.
Installing the MessageWay Server Maintenance Release:
1) Download the Maintenance Release install package sent by Progress and unzip.
2) Logon to the application server as the user that "owns" the MessageWay programs.
3) Locate the Maintenance Release tarball (messageway-6.1.0-mr09-solaris.tgz) in the Maintenance Release install package (...\messageway_mrs\solaris\) and copy to the application server.
4) Unzip the Maintenance Release tarball: gunzip messageway-6.1.0-mr09-solaris.tgz
5) Untar the resulting Maintenance Release tar file:tar -xvf messageway-6.1.0-mr09-solaris.tar
6) Step 5 will automatically create a new subdirectory named messageway-6.1.0-mr09-solaris.
7) Stop MessageWay.
8) If you have MWTranslator 6.2 installed, this manual step is required to save the 6.2 trm.so:
8a) cd /opt/messageway/bin/ (or equivalent) subdirectory
8b) cp -p trm.so trm-62.so (it will be copied back in step 17 below)
9) Logon as "root".
10) cd to the newly created messageway-6.1.0-mr09-solaris subdirectory.
11) Install the Maintenance Release by running the install script:./install.sh
12) Answer the prompts as they appear.
NOTE: New for this release, you will be prompted to select your database type:
Enter MessageWay DB Type MySQL(S) or Oracle(O)
NOTE: When Oracle(O) is selected, the following 3 prompts can be ignored by simply pressing the Enter key (they are not used at this time):
Enter DB Server Hostname (localhost) :
Enter DB Server Port (1521) :
Enter Oracle ServiceName :
The following prompt is also not used, but a value must be entered (any value will do):
Enter Oracle SID :
13) Log back on as the user that "owns" the MessageWay programs.
14) cd to the /opt/messageway/utils/ (or equivalent) subdirectory.
15) Convert the database to support new functionality by running the convert script:
./dbconvert -u -p -o dbconvertmr09.log
where is the user with access to the MessageWay database and
is the password for the user with access to the MessageWay database.
16) After dbconvert has finished, review the dbconvert.log and the dbconvertmr09.log to ensure the database was upgraded properly. These log files are located in the /opt/messageway/utils/ (or equivalent) subdirectory. Resolve any errors encountered in either log file before continuing with these instructions. An empty dbconvertmr09.log means that no errors were written to 'stdout', but errors may still have been written to dbconvert.log.
17) If you have MWTranslator 6.2 installed, this manual step is required to copy back in the 6.2 trm.so:
17a) cd /opt/messageway/bin/ (or equivalent) subdirectory
17b) mv trm.so trm-61.so
17c) cp -p trm-62.so trm.so
18) Start MessageWay logged on as the user that "owns" the MessageWay programs.
19) If you have MWReporting installed, this manual step is required to support 128 character Class Id's on datamart table messageshistory:
19a) Stop MWReporting.
19b) Logon to the database server where the MWReporting datamart (or equivalent) is installed as the "user" that owns
the datamart database.
19c)Run the following SQL command against your datamart database:
MySQL:alter table messageshistory modify ClassId varchar(128) character set ucs2;
Oracle: alter table messageshistory modify ClassId nvarchar2(128);
19d) Start MWReporting.
MessageWay - Issue #968 (Program changed: dbconvert.bin - version 6.1.0.6)
Issue 968: Increase column length of message attribute 'Class Id' from 64 to 128 characters on tables archivemessages, messages and messageshistory (if MWReporting installed). Changes: This problem has been fixed.
MessageWay - Issue #4100, 4101, 4241, 4356 (Program changed: MessageWay Installation Guide)
Issue 4100, 4241: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with Oracle 12c Release 12.2.0.1.0 using EasySoft odbc-oracle-3.6.0-linux-x86-glibc.
Issue 4101: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with mysql-server-5.7.23.el7 using mysql-connector-odbc-5.1.8-1.rhel5.i386.
Issue 4356: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with MQ Client version 9.0.5.0.
MessageWay - Issue #4100, 4101, 4241, 4356, 4366 (Program changed: MessageWay Users Guide and Reference)
Issue 4100, 4241: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with Oracle 12c Release 12.2.0.1.0 using EasySoft odbc-oracle-3.6.0-linux-x86-glibc.
Issue 4101: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with mysql-server-5.7.23.el7 using mysql-connector-odbc-5.1.8-1.rhel5.i386.
Issue 4356: Updated documentation to reflect that Ipswitch has verified that MessageWay works correctly with MQ Client version 9.0.5.0.
Issue 4366: Updated documentation to reflect that Ipswitch has enabled Public Key Authentication in MessageWay by default.
MessageWay - Issue #4226, 4304 (Program changed: mwimp.bin - version 6.1.0.6)
Issue 4226: Import of file system locations results in allowed access rights for each parent not being inherited by its immediate children. Changes: This problem has been fixed.
Issue 4304: Import of regular location folders with a location and folder underneath creates duplicate security records for the location. Changes: This problem has been fixed.
MessageWay - Issue #4322, 4326, 4330, 4342 (Program changed: mwuser - version 6.1.0.32)
Issue 4322: The View Logs security access right allows users to execute a Find Logs query, but it does not allow users to view individual log record details. Changes: This problem has been fixed.
Issue 4326: MWUser crashes with a seg 4 fault, core file is generated. Changes: This problem has been fixed. Also increased the request buffer size for all requests to MWUser from 32K to 64K to allow larger query requests.
Issue 4330, 4342: The Find Locations, Find Rules and Find Users options do not have a maximum rows returned value, resulting in unacceptable performance and/or the Manager becoming unresponsive when tens of thousands of rows are returned in the resulting query. Changes: The maximum rows returned value for the Find Locations, Find Rules and Find Users options has been hard coded to 10,000.
MessageWay - Issue #4203 (Program changed: mwimp.bin - version 6.1.0.5)
Issue 4203: Expand the 'Perform Message Actions' right to represent each action the current right controls. Changes: The 'Perform Message Actions' right has been replaced with ''Resubmit Messages', 'Redirect Messages', 'Release Messages', 'Restart Receive' and 'Cancel Messages' rights. Also, 'View Logs' right has been added to control access to Audit Logs, Event Logs and Trace Logs.
MessageWay - Issue #4041, 4080, 4158, 4198, 4203, 4225 (Program changed: mwsi - version 6.1.0.22)
Issue 4041: Decouple Service Interface session timeout from Manager timeout 'User Policies Logon Idle Lifetime'. Changes: New parameter SessionTimeout has been added to mwsi.conf for each separate listener section. This new parameter overrides Manager timeout 'User Policies Logon Idle Lifetime', which was previously used to timeout an SI listener session. Valid values are in minutes, and if not specified, Manager timeout 'User Policies Logon Idle Lifetime' is still used as the default.
Issue 4080: In the file system, users must incorrectly have download rights in order to upload messages. But what if user should only have upload rights but not download rights to file system mailbox? Changes: This problem has been fixed.
Issue 4158: FTP downloads fail when Class ID and NonStopCompat are both used. Changes: This problem has been fixed.
Issue 4198: SQL open cursor leak in service interface. Changes: This problem has been fixed.
Issue 4203: Expand the 'Perform Message Actions' right to represent each action the current right controls. Changes: The 'Perform Message Actions' right has been replaced with ''Resubmit Messages', 'Redirect Messages', 'Release Messages', 'Restart Receive' and 'Cancel Messages' rights. Also, 'View Logs' right has been added to control access to Audit Logs, Event Logs and Trace Logs.
Issue 4225: Transfer failure during a download results in message status being marked as Canceled instead of Available. Changes: This problem has been fixed.