Corrupt Access File

[DS]

PS... If I move to MySQL as a backend and keep Access as a frontend can I
still keep Acess's reporting abilities or do I have to go to Crystal
Reports? And....where do I get support on this thing? Newsgroup or Other.
Thanks
DS

 

[David W. Fenton]

will it be just tables will be in My SQL?

MySQL does not have a front end development system. It is only a
database engines, so, yes, only the tables would be in MySQL.

 

[David W. Fenton]

PS... If I move to MySQL as a backend and keep Access as a
frontend can I still keep Acess's reporting abilities or do I have
to go to Crystal Reports?

No, Access is still Access, regardless of what database engine it is
connecting to.

That is why Access is so useful -- it is completely agnostic about
the database engine in use.

And....where do I get support on this thing?

Depends on whether you use the community version (free) or the
enterprise version ($$$).

I honestly wouldn't recommend MySQL. It's really still a toy
database. And you have to be careful about which table format you
use, since transaction logging is only supported in the latest
version of one of the table formats.

 

[DS]

Well that 's defintly useful information! I would have moved to it
expecting logging. And if I got the wrong version....! So whic one would
you recommend if I need transaction by transaction back-up. Oracole? But I
heard that it's alot of maintance, something that can't be. I need
something simple to be able to bring it back to the last transaction if it
gets corrupted. Since I'm using Raid 5, I'm ok if the disk goes but not ok
if the file gets corrupted. Thats my fear.
Thanks
DS

 

[David W. Fenton]

Well that 's defintly useful information! I would have moved to
it expecting logging. And if I got the wrong version....! So
whic one would you recommend if I need transaction by transaction
back-up. Oracole?

Oracle is *extremely* expensive.

If you want a full-featured, industrial-strength inexpensive server
database, I'd go with PostgreSQL.

MySQL is fine for websites (i.e., mostly reads and few writes), but
I'd never use it for the kind of production data editing that my
Access apps use.

But I
heard that it's alot of maintance, something that can't be. I
need something simple to be able to bring it back to the last
transaction if it gets corrupted.

Er, that's contradictory of your goal of having a server back end --
transaction log restoration is *never* a simple task.

Since I'm using Raid 5, I'm ok if the disk goes but not ok
if the file gets corrupted. Thats my fear.

I think you're over-fearful of MDB corruption.

 

['69 Camaro]

Hi, DS.

So is this going to be easy?

Ease of data migration depends upon the skills of the database developer,
the complexity of the database application, and whether or not the database
was designed from the ground up with that particular back end in mind. In
your case, I suspect it's not going to be easy, because migrating the data
to a client/server database is an afterthought.

I would suggest getting formal training in the database engine you are going
to use. It would probably be quickest and easiest to learn SQL Server 2005
Express Edition if you don't have any training or experience in any of the
database engines that have free versions, because of the free training
videos, online training, online documentation, and strong newsgroup support
available.

Is it or will it be just tables will be in My SQL?

MySQL can only hold the tables, stored procedures, and views (equivalent to
queries). The presentation layer (forms, reports) and much of the
application logic (VBA code, macros) is in the front end.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Hi, DS.

PS... If I move to MySQL as a backend and keep Access as a frontend can I
still keep Acess's reporting abilities

Yes. The reports will still work with linked tables, regardless of whether
or not the linked tables reside in MySQL, Jet, SQL Server, Oracle, or
another database.

And....where do I get support on this thing? Newsgroup or Other.

Newsgroup support and online documentation are available. Regular support
is available for the non-Community edition of MySQL, but I don't know how
much it costs. Or you can get paid support from consultants. The online
documentation was the only thing I've ever needed, but I'm experienced in
database development and have formal training from Oracle University and
have taken both undergraduate and gradute level database courses.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.