andrew wrote:
(You can probably tell I've spent a lot of time being an editor!
Picky, picky! I'd be glad to help you on this, if you'd like, or just
shut up about all this petty stuff.)
Hi Barbara,
One of the tenants of a wiki is that the work is collaborative. For
example - When edit
(You can probably tell I've spent a lot of time being an editor!
Picky, picky! I'd be glad to help you on this, if you'd like, or just
shut up about all this petty stuff.)
Hi Barbara,
One of the tenants of a wiki is that the work is collaborative. For
example - When editing a page this i
andrew wrote:
Barbara Duprey wrote:
andrew wrote:
Hi,
I took the liberty of adding a page to the Base area of the wiki.
http://wiki.services.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures
Also updated the spreadsheet, available at my ftp server.
The function TRIM is now
andrew wrote:
Regina Henschel wrote:
Hi,
I've got a German Microsoft Access 2007 on WinXP Home. Now I try to
connect to the example database "Nordwind.accdb".
Using "Microsoft Access" on the first step of the wizard, doesn't
work, only .mdb-files are selectable.
Using "ADO" with provider
Regina Henschel wrote:
Hi,
I've got a German Microsoft Access 2007 on WinXP Home. Now I try to
connect to the example database "Nordwind.accdb".
Using "Microsoft Access" on the first step of the wizard, doesn't
work, only .mdb-files are selectable.
Using "ADO" with provider "Microsoft Jet
Hi,
I've got a German Microsoft Access 2007 on WinXP Home. Now I try to
connect to the example database "Nordwind.accdb".
Using "Microsoft Access" on the first step of the wizard, doesn't work,
only .mdb-files are selectable.
Using "ADO" with provider "Microsoft Jet 4.0 OLE DB Provider" is
I added the opening paragraphs to the wiki page per the last email.
Fixed the TRIM function entry - problem was the standard way of showing
options [opt | opt | opt ] is also meaningful code to the wiki...arrrgh.
Haven't dropped that Direct column yet. ( or fixed the spelling for
Designer eit
andrew wrote:
Barbara Duprey wrote:
andrew wrote:
Hi,
I took the liberty of adding a page to the Base area of the wiki.
http://wiki.services.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures
Also updated the spreadsheet, available at my ftp server.
The function TRIM is now g
Barbara Duprey wrote:
andrew wrote:
Hi,
I took the liberty of adding a page to the Base area of the wiki.
http://wiki.services.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures
Also updated the spreadsheet, available at my ftp server.
The function TRIM is now grouped with str
Marc Santhoff wrote:
Executing CHECKPOINT DEFRAG from the SQL window will indeed shrink the
size of the odb file,
Doing so with in a script with
oStatement.ExecuteUpdate( "CHECKPOINT DEFRAG" )
does not. It runs to completion, but the file size is not changed.
Not wanting to insult anybody
andrew wrote:
Hi,
I took the liberty of adding a page to the Base area of the wiki.
http://wiki.services.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures
Also updated the spreadsheet, available at my ftp server.
The function TRIM is now grouped with string functions, and I ad
Hello Barbara,
> ... and that's exactly what I did, once I found the TRIM description in
> the HSQLDB documentation. (You may not have seen my note about that,
in fact I missed it, sorry.
> So I can see that the argument could be left out, but how does it
> identify which possibility is the de
Am Samstag, den 25.08.2007, 11:34 -0400 schrieb andrew:
> > So you can do so either in the SQL window or in a script with
> >
> > oStatement.ExecuteUpdate( "CHECKPOINT DEFRAG" )
> >
> > Drew
> Well, it turns out with a little further testing that this is not
> exactly the case.
>
> Executing CH
I think I need to catch up on my reading.
I've tested both SQL methods for compacting the database. Both work,
although the CHECKPOINT DEFRAG seems to be the better approach as the
file doesn't have to be closed and reopened.
Preliminary impressions seems to indicate a performance improvement
Hi,
Also updated the main Base page to include a link to the SUN Report
Builder Page
Updated the SUN Report Builder page to include categories: Database,
Base Documentiaton
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
Hi,
I took the liberty of adding a page to the Base area of the wiki.
http://wiki.services.openoffice.org/wiki/Built-in_functions_and_Stored_Procedures
Also updated the spreadsheet, available at my ftp server.
The function TRIM is now grouped with string functions, and I added the
statistical
andrew wrote:
The other day the question came up about recovering space from deleted
records in a Base ( embedded ) database.
I mentioned using the command
SHUTDOWN COMPACT
in the SQL window, and that you would need to close and reopen the
Base file.
You can also use this command
CHECKPOINT D
The other day the question came up about recovering space from deleted
records in a Base ( embedded ) database.
I mentioned using the command
SHUTDOWN COMPACT
in the SQL window, and that you would need to close and reopen the Base
file.
You can also use this command
CHECKPOINT DEFRAG
without t
Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
Hmm. In the Execute SQL Statement dialog, I had
UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
What I got was an error:
2: Unexpected token in statement [UPDATE "Addresses" SET ADDR = TRIM ( ADDR]
Note that it seems to have dr
Frank Schönheit - Sun Microsystems Germany wrote:
So, the complete syntax if you want to use TRIM is
UPDATE "Addresses" SET ADDR = TRIM ( BOTH FROM ADDR )
where you can even omit the BOTH.
Ciao
Frank
Almost. TRIM( FROM ) works in SQL View, but not in Designer View.
It generates a warni
Hello Barbara,
> Hmm. In the Execute SQL Statement dialog, I had
> UPDATE "Addresses" SET ADDR = TRIM ( ADDR )
>
> What I got was an error:
> 2: Unexpected token in statement [UPDATE "Addresses" SET ADDR = TRIM ( ADDR]
>
> Note that it seems to have dropped the closing paren, and the preceding
21 matches
Mail list logo
