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


Hi :)
They all left.  The people that are using the system are not the ones that set it up.  I think part 
of the idea was that we would have to pay the previous people a consultancy fee in order to do 
fairly normal stuff.  Now it's my turn to create even more confusion by creating forms that are 
called things relevant to what they do.  In our Access forms we have 1 called "Organisations-~" and 
the one thing i can guarantee it doesn't show is anything to do with any organisation.  lol
Regards from
Tom :)



--- On Wed, 14/3/12, drew jensen <drewjensen.inbox@gmail.com> wrote:

From: drew jensen <drewjensen.inbox@gmail.com>
Subject: Re: [libreoffice-users] Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
To: users@global.libreoffice.org
Date: Wednesday, 14 March, 2012, 13:16

On Wed, 2012-03-14 at 13:12 +0000, Tom Davies wrote:
Hi :)
Ahhhah.  Right.  Ok, so it sounds as though i could at least give it a go and see what it looks 
like.  So far i have been a bit scared of even trying.  

So, first step for me is to back-up the Access file and see if i can get Base working with that.  
The Access we have at work is a mess of too many Queries let alone tons of Forms and Reports that 
no-one uses.  It's just a huge pile of confusing mess.  It would be good to start again with Base 
but everyone is extremely paranoid about the whole thing.  "We don't understand it so don't 
touch" 
Many thanks and regards from

Ok but keep in mind that the same people that made that pile of mess are
likely the ones to make the next pile of mess - in other words it may
not be the technology that needs changing.

Tom :)


--- On Wed, 14/3/12, drew jensen <drewjensen.inbox@gmail.com> wrote:

From: drew jensen <drewjensen.inbox@gmail.com>
Subject: Re: [libreoffice-users] Re: [libreoffice-documentation] Chapter 2 of Base Guide progress
To: users@global.libreoffice.org
Date: Wednesday, 14 March, 2012, 12:57

On Wed, 2012-03-14 at 12:49 +0000, Tom Davies wrote:
Hi :)
So Base can't update Accesses internal tables?

That is NOT what I said.

What I said was, that when connecting to an MS Access file the users
need to be mindful of the fact that queries in the Access file will
appear to them to be tables or views in the Base interface.

//drew




-- 
For unsubscribe instructions e-mail to: users+help@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




-- 
For unsubscribe instructions e-mail to: users+help@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

-- 
For unsubscribe instructions e-mail to: users+help@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.