Hope it's intresting...

zym1ne

Registered User.
Local time
Today, 09:21
Joined
Jul 25, 2003
Messages
34
Hope this piques someones interest here...

Finally managed to stumble through my first DB design nightmare experience :)

Having survived (just abouts) am just wrapping up some loose ends and can't figure out the exact process for the following:

Sales reps create work requests for me to call in on Dealers, they enter the info via a form (frmWorkRequests).

What I would ideally like to achieve is for them to produce all thier work requests on a daily basis and then via e-mail them to me, effectively taking all the info from the requests tbl and sending it to me, from there I can import these e-mails into my requests tbl and view them within my own DB via a lookup form based on my tblWorkRequests Query...

I know this might be a bit sketchy but if it makes enough sense then would be great if someon could give me a hand in the right direction :)

As to the fact that I finally reached this stage of the design, I would just like to say a BIG thanks to all who got in touch and helped with my earlier questions, could'nt have acheived it without you lot...this is the top of all forums out there :)

zym
 
zym,

I don't think that you want them to email your and then try
to import that into your db. Wouldn't it be easier to just
link to their table tblWorkRequests and cut out the "middle man"?

Wayne
 
Have no connection

Hi there Wayne

At mo I have no current connection with them, all machines are Stand-Alone and not on Network, plus most of them will work from home which could be anything up to 90miles away or more.

E-Mail just seemed liked the easiest and most sensible route to take really?

But maybe I might be barking up the wrong tree here, open to any suggestions tha might present a better solution and achieve same results :)

zym
 
zym,

If at all possible, it would be better to get your data from nice
Access tables (instead of email).

If they could email you their dbs, you could collect them in
a folder and process them (then move, rename, or delete them).
That would make it far easier to find out whether data is an
update or new transaction.

Plus, the email route will require parsing the file and I don't
see any guarantee that their format would be static. For example,
suppose one of them puts a note at the end that says, ignore
the second transaction from the bottom?

Just some thoughts ...

Wayne
 

Users who are viewing this thread

Back
Top Bottom