[GRLUG] Access->MySQL with GUI

Szymon Machajewski SMachaje at grcc.edu
Thu Jun 15 08:15:30 EDT 2006


Sounds good.  Please let me know how it turns out.

Szymon Machajewski

Solutions Engineer / DBA
Red Hat Certified Engineer
Microsoft Certified Solution Developer
www.grcc.edu/smachaje 


>>> billl at mtd-inc.com 6/14/2006 10:24:32 pm >>>
Thanks for everyones suggestions.
I've decided to go with DBACentral for a few reasons.
Low cost ($125).
It will convert my Access DB tables and queries to MySQL, and provides
a 
runtime version including 5 users that displays the converted Forms. 
Since my target users are all using Windows this is ideal for 
performance reasons and getting running quickly. I plan to run MySQL 5

on OpenSUSE 10.1 for the backend.
DBACentral can also generate PHP pages for the forms, which would allow

me to migrate later on to a completely standardized and open platform.

For my purposes in this project, OOBase would not be ideal since it 
requires the full install of OO.
(I really wish they would split the apps up)
I would really love to hear of anyones success in converting a complete

DB to OOBase however.

Bill


Szymon Machajewski wrote:
> I've had hard time importing Access database into OOBase.  I can
link
> the database to Access file easily, but I want to 'convert' Access
> database to  OOBase.  Any idea how to do that?
>
> Re-creating is what I'm trying to avoid.
>
> Szymon Machajewski
>
> Solutions Engineer / DBA
> Red Hat Certified Engineer
> Microsoft Certified Solution Developer
> www.grcc.edu/smachaje 
>
>
>   
>>>> jodanlime at gmail.com 6/14/2006 1:18:31 am >>>
>>>>         
> why not just use open office Base? its open source, and can create
> everything your asking it to. I haven't used it much, and I'm
nothing
> of a
> database expert, but after learning access for 2 years (waste of my
> time =P)
> I found Base to be very easy to adapt to.
>
> On 6/13/06, Szymon Machajewski <SMachaje at grcc.edu> wrote:
>   
>> You have to separate GUI from the actual database (tables).
>>
>> What I would suggest is moving the tables to MySQL and keeping the
>> Access GUI (forms, reports etc).
>> The easy way is to use a tool (like SQLYog) which allows you to
>>     
> export
>   
>> Access tables into MySQL server.
>>
>> Once tables exist in MySQL server you simply connect via ODBC
Access
>> (linked tables) to the MySQL server.  So when you open Access your
>> tables will be from MySQL and GUI from Access.  This way you can
>>     
> connect
>   
>> a number of thick clients (Access GUIs).
>> At the same time you can work on an alternative GUI.  Maybe use PHP
>>     
> or
>   
>> another language to provide online access to the database.
>>
>>
>>
>>
>> Szymon Machajewski
>>
>> Solutions Engineer / DBA
>> Red Hat Certified Engineer
>> Microsoft Certified Solution Developer
>> www.grcc.edu/smachaje 
>>
>>
>>     
>>>>> billl at mtd-inc.com 6/13/2006 12:18 pm >>>
>>>>>           
>> Could someone give me a pointer for "Moving MS Access databases to
>> MySQL server while keeping the GUI"? that's been brought up
>>     
> recently.
>   
>> I need to rebuild an Access DB for use by multiple sites
>>     
> concurrently
>   
>> and have it pull data from an Oracle DB.
>> I don't want to use Access for a frontend if I can help it.
>>
>> Google shows lots of options.
>> http://microolap.com/products/database/mydbacentral/ looks
promising
>> for commercial.
>>
>> A pointer in the right direction would be greatly appreciated.
>>
>> Bill
>>
>>
>> _______________________________________________
>> grlug mailing list
>> grlug at grlug.org 
>> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug 
>>
>> _______________________________________________
>> grlug mailing list
>> grlug at grlug.org 
>> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug 
>>
>>     
> _______________________________________________
> grlug mailing list
> grlug at grlug.org 
> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug 
>   



More information about the grlug mailing list