replacing Access db with SQL Server db

Hi,
We are currently using a couple Access 2002 databases
that were recently converted from Access 97. The
databases are located on a Windows 2000 server and
accessed from Windows XP Pro workstations. One of our
databases has a loader program that looks in a particular
directory for some .txt files, then uploads them into an
Access table. Since upgrading, a message says that it's
an unrecognized database format. The loader was built to
work with Access 97 and is not working with 2002. The
programmer that created the loader program does not have
the latest versions so he can't help me. Can someone
give me any ideas on how to go about correcting this.
The other option would be to move the database into SQL
Server and use Access as front end, but I would still
need a 'loader' program and would not know how to create
it.
Does anyone have ideas, suggestions? If further
information is needed, I'd be happy to supply it.
Thanks in advance for your expertise.
D.If the loader is itself an Access db, find a consultant that will upgrade it
for you...sounds easier than doing a SQLServer conversion. If you go to SQL
Server, you can likely dump the loader and use SQL's built in DTS utility to
load the txt files
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
<anonymous@.discussions.microsoft.com> wrote in message
news:a67601c406cd$ee46b490$a501280a@.phx.gbl...
> Hi,
> We are currently using a couple Access 2002 databases
> that were recently converted from Access 97. The
> databases are located on a Windows 2000 server and
> accessed from Windows XP Pro workstations. One of our
> databases has a loader program that looks in a particular
> directory for some .txt files, then uploads them into an
> Access table. Since upgrading, a message says that it's
> an unrecognized database format. The loader was built to
> work with Access 97 and is not working with 2002. The
> programmer that created the loader program does not have
> the latest versions so he can't help me. Can someone
> give me any ideas on how to go about correcting this.
> The other option would be to move the database into SQL
> Server and use Access as front end, but I would still
> need a 'loader' program and would not know how to create
> it.
> Does anyone have ideas, suggestions? If further
> information is needed, I'd be happy to supply it.
> Thanks in advance for your expertise.
> D.