[AccessD] MZTools Letdown!

[John Colby]

I would bet that this is a limitation (bug) in Access itself.  AFAIK Access
(JET) does the export and import.



On Fri, Jul 12, 2019 at 1:32 PM Bill Benson <bensonforums at gmail.com> wrote:

> Just discovered MZTools does not import objects properly into MS Access
> 2013 database. Here is what I wrote to the vendor.
>
> This just came to my attention today and I think it is a pretty serious
> failing. When I exported modules and did some editing of them in WinMerge
> then imported the altered files back into MS Access database, the following
> problems were observed:
>
> MS Access forms are not imported. Their code comes in ok as Class1, Class2,
> etc. This is a defect that can be lived with except that it is not always
> clear what the correspondence is between Class1 and whatever form that code
> is representative of.
>
> MS Reports - the code does not come in AT ALL. Why doesn't the code come in
> as Classes at least? Would have the same difficulty in terms of
> correspondence between report name and new Class module names, but at least
> the code would be present. AND THERE IS NO WARNING about this.
>
> Standard and Class Modules... New modules come in but old existing modules
> do not get overwritten and instead they come in with a numeric increment in
> the name. Therefore what I had to do was manually remove all class and
> standard modules, and then import them.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting