On Sun, 2017-12-03 at 16:48 +0100, Robert Großkopf wrote:
> Hi Harvey,
> >
> >
> > I've got it. The hsqldb driver pool had to be enabled in the Base
> > options settings.
>
> Have never touched there anything. The conneection-pool is disabled
> here.
> Do you use the LO-version from OpenSUSE or
Hi Harvey,
>
> I've got it. The hsqldb driver pool had to be enabled in the Base
> options settings.
Have never touched there anything. The conneection-pool is disabled here.
Do you use the LO-version from OpenSUSE or do you use LO downloded
directly from LO-website?
I prefer the version from
Macro will be executed here and update to 2,4,3 will be executed.
Hallo Robert,
> > Don't know what is going wrong there with your installation.
> >
> > If you have opened the table at the same time you have to refresh
> > the
> > data of the table afterwords - but if you don't see the
On Sun, 2017-12-03 at 09:37 +0100, Robert Großkopf wrote:
>
> > Hi Robert,
> >
> > I think I can see what you are trying to do, but nothing happens on
> > clicking the button.
>
> First there should appear a messagebox with question: "Should the
> code
> ... be executed?"
> If you click "yes"
Hi Harvey,
>>
>> here is a little example-database for executing SQL by a macro.
>> http://robert.familiegrosskopf.de/download/Example_InsertUpdateDelete
>> _SQL.odb
>> Open the form and try. Could be constructed a little bit better, but
>> works when code is right.
>>
>> Regards
>>
>> Robert
>
>
On Sat, 2017-12-02 at 20:57 +0100, Robert Großkopf wrote:
> Hi Harvey,
>
> here is a little example-database for executing SQL by a macro.
> http://robert.familiegrosskopf.de/download/Example_InsertUpdateDelete
> _SQL.odb
> Open the form and try. Could be constructed a little bit better, but
>
Hi Harvey,
here is a little example-database for executing SQL by a macro.
http://robert.familiegrosskopf.de/download/Example_InsertUpdateDelete_SQL.odb
Open the form and try. Could be constructed a little bit better, but
works when code is right.
Regards
Robert
--
Homepage:
On Sat, 2017-12-02 at 10:42 +0100, Alexander Thurgood wrote:
> Le 01/12/2017 à 23:08, Harvey Nimmo a écrit :
>
> Hi Harvey,
>
> You are correct, it would improve the user experience of Base by an
> important measure to have a GUI UPDATE capability. This is something
> that has been desired by
Le 01/12/2017 à 23:08, Harvey Nimmo a écrit :
Hi Harvey,
You are correct, it would improve the user experience of Base by an
important measure to have a GUI UPDATE capability. This is something
that has been desired by users since the days of StarOffice, through
OpenOffice.org to the present day
On Fri, 2017-12-01 at 19:56 +0100, Robert Großkopf wrote:
Hi Robert,
I appreciate your comments! Many thanks.
> What you perform with the query-editor isn't a query. A query
> shouldn't
> change the content of any table.
From a purist viewpoint, you are right, of course! My mind has been
Hi Harvey,
>
> Obviously, I found this behaviour (by accident) because I was looking
> for it, and because I needed it. Also obviously, my feeling is that
> LOBase is not doing itself a favour by restricting usage of SQL in this
> way. I would prefer a feature that allowed data manipulation via
>
On Thu, 2017-11-30 at 15:50 +0100, Robert Großkopf wrote:
>
> ...
>
> It has never beeen intended that the query-editor is used for
> changing
> data. There is a feature-request for this:
> https://bugs.documentfoundation.org/show_bug.cgi?id=31398
> since 7 years.
> The risky feature is: the
Le 30/11/2017 à 15:50, Robert Großkopf a écrit :
> If we write a bug-description about this the solution at this moment
> could be the "feature" of the direct connection will be taken away
> instead of changing something in the GUI, which works right with
> internal Database and other external
Hi Harvey,
>
> I am accessing a backend Mariadb V10 on a backend server via
> MySQL(Native).
>
> The Base query contains only the following statement:
> UPDATE Family.Adressen SET Print_flag = FALSE;
>
> LO Version 5.3.5.2 from OpenSuse on Linux.
>
Have tested this with nearly the same
On Wed, 2017-11-29 at 18:43 +0100, Robert Großkopf wrote:
> Hi Harvey,
> >
> >
> > The UPDATE query is allowed (i.e. stored in the queries list) if
> > you
> > 'edit in SQL view' and then set the 'Run SQL Command directly' in
> > the
> > SQL editor. If you don't do it this way only SELECT
On Wed, 2017-11-29 at 18:43 +0100, Robert Großkopf wrote:
> Hi Harvey,
> >
> >
> > The UPDATE query is allowed (i.e. stored in the queries list) if
> > you
> > 'edit in SQL view' and then set the 'Run SQL Command directly' in
> > the
> > SQL editor. If you don't do it this way only SELECT
Hi Harvey,
>
> The UPDATE query is allowed (i.e. stored in the queries list) if you
> 'edit in SQL view' and then set the 'Run SQL Command directly' in the
> SQL editor. If you don't do it this way only SELECT queries are
> permitted.
If I try this the message appears:
Statement does not
Hi Alex,
The UPDATE query is allowed (i.e. stored in the queries list) if you
'edit in SQL view' and then set the 'Run SQL Command directly' in the
SQL editor. If you don't do it this way only SELECT queries are
permitted.
Cheers
Harvey
On Wed, 2017-11-29 at 14:34 +0100, Alexander Thurgood
Le 29/11/2017 à 12:27, Harvey Nimmo a écrit :
Hi Harvey,
Perhaps I am misunderstanding the issue here, but the panel you refer to
is only supposed to be a Preview of the document display. So, if you
execute a query then you get a preview of the result, which to me, would
seem to be "functioning
19 matches
Mail list logo
