Question Locked

Access and Word, XML and the Novice... Oh my!

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have something of a quandary at my place of employment, and was wondering if anyone could help me find a solution to it...

The thing is, we're a construction firm that has been collecting data on addresses, customers, etc for 14 years. Right now, we have everything in folders in windows explorer. It is my task to create a database to catalouge all of the information in such a way that queries can be run on it, et al. The main challenges are:

1) a mess of legacy data stored in several thousand individual word forms.
2) the fact that the information is constantly updated, that is, new records would have to be added by the end users every day (every time an inspection was taken)-- we have information collected on one form that would need to go into several different tables, if not different databases.

I have no problem with inputting old data by hand-- but I only want to do it once. Also, I think XML holds the key to this solution, but I'm very, very new to it.

I've had Microsoft infopath suggested to me, but if I'm not mistaken, would not each end user have to have their own liscenced copy? Small businesses tend to get edgy about things like that.

Anyone have any ideas? Thanks in advance,

~Rabbit

3 replies

by tony hopkinson

databases if you want to report a cross more than one, that will just complicate things.

Big question what do the documents look like

free format, word tables? tab delimited ?

if it's the former very little is going to help you aside from maybe word search if you are really lucky. The latter two you have a chance. XML won't do that much for you by itself, you still need to identify the content you want to keep.

If they were already XML, then you wouldn't have a problem. Or csv or fixed format or anything but word documents.

New records, if they are only adding. Archive what you have making it read only and empty the current ones.

Personally I'd just set up a new system, access, mysql, msde, SQL express, a csv file and start trying to collect the new data and look at getting the old stuff in by hook or crook.

Be careful on this sort of exercise, you can spend masses of effort trying to import the legacy data, when it would have been cheaper to hire a temp and have them type it in.

Also don't design a system that will cope with the current implementation instead of the implementation you would like.

by absolutely

First, figure out your database structure. Define fields in MS Access, data types, relationships, the whole works, with all blank tables.

Make a copy.

In the copy, enter a representative sample of the data for one hour.

Estimate the fraction of the work you've completed, in order to determine how many temps to hire for a weekend, or if you work weekends, more temps, overnight.

Measure twice, cut once, same in every industry.

This discussion is closed to new replies.