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


Hi :)
I keep meaning to give the link to the "Professional Support" page but i
have a wedding shoot to prep for and keep forgetting.

http://www.libreoffice.org/get-help/professional-support/

Hopefully it mentions Collabora which 'recently' budded off from SuSE as
had been planned for years.  Many companies pay devs, either in-house or as
external consultants, to work on LibreOffice.  It's more cost-effective
(and much cheaper) than paying for licenses for a product which may never
deal with their pet-issues.  SuSE seemed to have more devs working on
LibreOffice than most other companies.  So my guess is that Collabora are
probably about the best professional support it's possible to get for
LIbreOffice!

If you need professional support for a wider move to FOSS then you might
get that from one of the other companies listed, for example Canonical or
Redhat (there is also the "Free Software Foundation", but i have no way of
knowing or guessing which is best for your specific case.

Regards from
Tom :)



On 11 August 2014 21:23, Jim Byrnes <jf_byrnes@comcast.net> wrote:

On 08/11/2014 03:05 PM, Stefan Gruber wrote:

Hello,

Jim Byrnes schrieb am Sonntag, 10. August 2014 23:47:

A couple of questions:

(1) Has anyone here used it and does it make writing macros for Base
easier?


I looked at the examples a few weeks ago, and it seemed to me as a
clearer approach to database programming as the UNO-way.

IMHO it is not only useful for migrations from Access, but for more
serious db-projects. I do not know anything about MS-Access-Programming,
I did some old-style DBase/FoxPro-Development some years ago and I
didn't  feel well with this UNO-thing up to now.
Obviosly it is a great API, but that huge that it becomes a labyrinth to
me.


I agree, it looks much cleaner. Every time I try to work with UNO, I think
what an overly complex way to accomplish what is sometimes a fairly simple
task.  The only thing wrong with Acess2Base is that I do all my work with
Calc.  That's why I was wondering if there was going to be a Excel2Calc
version.


 After Access2Base was incorporated in LO from 4.2 on, it is a promise to
improve things and it might become real, if it would be featured as the
standard way of programming LO Base and if gets broader acceptance.

At this time I can't estimate, wether I can rely on this tool for long-
term projects.
And there is yet a lack of documentation, tutorials for end-users.

Fortunately there are more discussions about Base in general in the last
months here.
I wonder why this topic came up so "late"...


I would guess that, probably because of UNO, not that many people are
writing macros.

Regards,  Jim





--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-
unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.