Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index

I have time to fix the styles and formatting in chapter 9, Macros, but I
don’t know enough about macros to review the content.


On Sun, 5 Apr 2020 at 15:20 <> wrote:

Hi Pulkit

I do not have much knowlegde of Base and also no affinity with it.
So I do not no if I am the one to review a chapter of the Base Guide.

Greetings, Kees

Pulkit Krishna schreef op 04.04.2020 12:50:
Hello Kees,
Steve said that he can't take macros chapter of base guide for review.
hope you can take it. (See my previous email).
Pulkit Krishna

On Sat, Apr 4, 2020 at 2:54 PM Pulkit Krishna

I know that Robert but Drew has taken the file for around 20-25 days
he is not answering to any of my emails. I think he is busy.
Pulkit Krishna

On Sat, Apr 4, 2020 at 2:52 PM Robert Großkopf

Hi Pulkit,

I think that Drew is extremely busy at the moment and cannot have the
review of chapter 9 macros. I see that Stephen and Kees had done the
and second review of the macros chapter of the getting started guide.
you both please also review the macros chapter of Base guide?

Drew wanted to add content to the chapter about Access2Base. I have
written only a few rows about this possibility to create macros,
I don't know anything about macros in Windows and macros in Access
don't need to use this feature.



To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.