Well, that changes a lot. Remember that Base is a front end to many
backends, and what you can do in that front end also changes - though
not dramatically - based on the particular backend. In the case of MS
Access (Jet) there is appears to be IMO a lot of shortcomings (due I
would guess in no short reson to Jets querky SQL syntax) , in the case
of MySQL there are quite a few less and you could for example enter your
concatination directly in the GUI builder using the concat function.
The same holds true if you migrated your data from the MDB to a Base ODB
file itself. The big question there would be whether you need concurent
multi-user support?
Shane Johnson wrote:
Thank you, all of you, for you replys. One more question on this
then. With having to do all the formulations in the query in SQL, how
much of a benefit does the Base GUI offer? Would I be better off just
using MySQL?
Thanks
Shane
Andrew Jensen wrote:
Sorry, for the tack on post, but the point I meant to make with this is:
You are moving your front end from Access so, you should be able to
use the Access GUI query builder to generate your queries. Access
offers you a SQL view of the query. You should be able to copy this,
and paste into a Base SQL view query object, since this SQL view in
Access is really the Jet engine dialect.
Andrew Jensen wrote:
Yes, and kind of no. You can start with GUI functions and select
your fields and handle your joins. But then you must turn the
designer off and finish the part with the concatination by hand.
Just so you know it also means that you can enter it as more
standard Accesseeze also, this statement would be just as valid with
SQL direct turned on
SELECT [FirstName]+ ' ' + [LastName] AS [Name] FROM [Customers]
By the way, the above select staetment is what is actually generated
by the MS Access query builder when you enter
Name: [Firstname] + ' ' +[LastName]
in the field area of the designer and sent to the Jet engine.
Because Base is a loosely coupled front end [i](My terminology
there)[/i] to any number of backends it is the syntax that is
accepted by the MS Jet engine that you need to enter, not the syntax
you enter in the MS Access GUI, since MS Access itself is just a
front end to the Jet engine, albeit a very tightly coupled front end.
This also means that once your make the final changes you can not
turn the designer back on, it will report a syntax error.
Shane Johnson wrote:
Thank you Drew. I will give that a try. Will have have to build
the whole query with SQL or can I just do the column I need to modify?
Thanks
Shane
Andrew Jensen wrote:
Hi shane,
Using OO 2.0.1 on WinXp and connecting to a MS Access database I
can perform a cancatination such as this:
SELECT `FirstName` & ' ' & `LastName` AS 'Name' FROM `Customers`
`Customers`
You must run this query as 'Run SQL Direct', which in the Query
builder is the button with a green check mark over the letters SQL.
HTH
Drew
Shane Johnson wrote:
Good Afternoon. I was referred here from the OOo users
group. The following is a paste of the message I sent to that
list. If anyone can help me I would appreciate it.
Thank you
Shane
I am converting from Access to Openoffice and was trying to run
a query
against a ODBC source. In Access I could do something like the
following
fieldname: [table:Data1] + [table:Data2}
and have it spit out a concatenated result. I tried this in
Base and it
will not let me do this. Did I miss something or is there a
different
way to do this.
I am running 2.0.1 on Win2K.(Let me know if you need more info)
I went through the how-to on Base and it didn't really help. If
there
is some other resource you could point me to that I couldn't
find, that
would be appreciated as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]