Use or convert- Access 97 backend with Access 2003 runtime front e

G

Guest

I've changed the front ends of our applications to Access 2003 runtime. Now I
can change the backend- is there a good reason to do that or should I just
keep it in Access 97? We have about 20 users at a time- some are just making
a note to a customer order and 3-4 are logging items on an order as they are
packed. The data entry for the orders comes mostly when we download .csv
files from our ecommerce site twice a day and import them- takes about 5-10
minutes each time. We do have some issues where somone is blocked and has to
wait for someone else to get done. I'm hoping to change to SQL Server 2000
next summer. What would be the best to do- go to Access 2003 back end, then
to SQL Server, or wait until I can do SQL Server?
Thanks
 
D

Douglas J. Steele

I don't see any overwhelming reason to go to 2003 then SQL Server unless you
require Unicode.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MS Access Front End - SQL Server Backend 7
Access to remote SQL server 14
Multiple Access and ODBC connections 3
Convert Superbase 3.0 front-end db to Access 2003 db 1
Access 97 Runtime with Access 2000 installed 7
Call Report from SSRS 4
Upgrading backend from Access 97 to sql server 18
Access 2003 front end with sql 2005 backend 7

Top