a2k upgrade back end advice required

[SKG]

Hi all

We currently use a split A2k database system with about 10,000 clients
/ 45,000 orders / 90,000 order entries etc with about 17 users (only 8
users do editing)

We currently upload data to a internet search engine via a 4d database
by means of exporting text files from access into 4D and then uploading
to the web, however the web site search engine needs a major overhaul
as it currently sees data in a flat file format only which is
cumbersome for searching etc

The access system has grown into a bit of a monster and probably needs
to be re written, however before we undertake this I wondered if it
would be about time to upgrade the back end

Has anyone got any upgrade advice on changing the back end from
Access/jet to something like MySQL or SQL Server (or soemthing else)
bearing in mind the learning curve involved.
i am still keen to keep access as the front end

many thanks

Steve

[Albert D. Kallal]

"SKG" <st***@dentonsd irectories.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Hi all

We currently use a split A2k database system with about 10,000 clients
/ 45,000 orders / 90,000 order entries etc with about 17 users (only 8
users do editing)
Sounds like you got a good working system, and it serves you well!!
Has anyone got any upgrade advice on changing the back end from
Access/jet to something like MySQL or SQL Server (or soemthing else)
bearing in mind the learning curve involved.
i am still keen to keep access as the front end

There has been a free edition of sql server included with the last 3
versions of access. However, that free edition has limitations in terms of
performance.

It seems to me that using a server based back end could solve both the web
systems problems, and also make moving of data from your existing
application to the web server. In fact, the whole process could be made
automatic and run on a scheduled basis without human intervention.

The best free database I know right now is MS sql express. You can find out
about it here:

http://lab.msdn.microsoft.com/express/sql/default.aspx
There is quite a few postings in the newsgroups on migration, and here is
some additional thoughts

http://www.granite.ab.ca/access/sqlserverupsizing.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl************* ****@msn.com
http://www.attcanada.net/~kallal.msn