[AccessD] Backend database corruption

Hi Arthur,

Not still working on this one.  But, I do have another one that I 
inherited, and it does need to be split.  I will make use of all the 
guidance I can get from my AccessD colleagues in order to get that one 
done right.  Thanks for the advice and information.

TNF

Tina Norris Fields
tinanfields-at-torchlake-dot-com
231-322-2787

On 2/22/2015 12:28 PM, Arthur Fuller wrote:
> Tina,
>
> Are you still working on this project? If not, then suggestions are
> academic. If so, then the first thing to do is split the database! Put a
> Front End on each client station and leave the BE where it is.
>
> IMO, next thing to do is convert the BE to either SQL Express or MySQL.
> Incidentally, a company called Bullzip <http://www.bullzip.com> offers a
> pair of great tools that convert Access databases to either MS SQL or MySQL
> -- and they are free. Once the database is converted, set up a new instance
> of the FE that uses ODBC to connect to the new database.
>
> Depending on the complexity of the Access BE, converting the FE to address
> the new database can be trivial (where forms and reports are bound directly
> to tables), or more involved (converting Select data sources to named
> queries, which will arrive in the new BE as Views).
>
> In the case of SQL Express, you'll need SSMS (the database manager) or SQL
> Bench (the MySQL database manager).
>
> While "graduating" to a real DBMS on the back end, you can leave the
> current (split) database in place, until you get the new system working.
> Splitting the old database will help significantly in preventing
> corruption. And as previously mentioned, you have to replace the wi-fi with
> wired connections.
>
> Migrating the current DB to a real DBMS won't  take long, really.
>
> Arthur
> ​