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


I am tasked with writing a quick fix replacement for a very old dbase
application running on WinXP.  I am considering using LO Base with ODBC(SDBC?)
to connect to a Postgresql-9.1 RDBMS hosted on a Linux server.

Assuming that I can get the connectivity between LO on the MS-Win desktops and
the PostgreSQL-9.1 instance on the Linux server host I intend to use the forms
capability of LO to provide the user interface.  Which leads me to my
question.  Is there any testunit-like or Rspec-like framework for designing
and building LO user interfaces;  particularly for testing input forms and
such?

Are there any issues with respect to Multi-User access via LO forms across
ODBC/SDBC to PostgreSQL that I should be made aware of?

-- 
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


-- 
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.