Hi Paul,
Ops, I’m sorry I posted the file as a different post; I didn’t know
how to do it following the original! I definitely agree with you,
a .vbs operated centrally after end user signs off on his
data entry. Then if I understand, user will sign off by exporting part
of the Tracking sheet to a
Hi Cecilia,
After checking out your excell workbook, IMHO the best is to develop
a .vbs that does both things: grab the specified data in the different
excel files and insert them in the database. Still this problem: if
the end user starts this .vbs, he must have access to the database;
else i the
Paul,
Thanks again, I really appreciate your help. I will send another post
with an Excel file to use as an example. Since the DB is not developed
yet, and I am finishing the Excel tool, we are in the perfect world;
we can decide how to handle.
You will see in the Excel a main sheet called Tracki
There are two sides:
a) the user side: if a1:b20 is all the sheet contains, the user could
save his sheet as "user.csv" in a particular folder
but if the range to import in access is only part of the sheet, maybe
I could develop a little macro to export only that part... You tell
me !
b) the centra
Hi Paul,
I'm glad that you have an option to deal with this. Yes, I am fully
open to your suggestion, each user exports as .csv in a shared drive
and then I import in my Access database, in my computer.
I will really appreciate your help/guidance on this. I don't know
where to start, I never worke
Hi Chechu,
Why not export that particular range in a .csv file, that would be
stored in a dedicated folder on the network, and imported by Access on
its own time...
You need the macro to export the range in Excel, and a macro in Access
to check for those files and import them...
If that idea suits
