Stump the Panel » End Users and Information Workers

Automating upload of client-side file creation date/author data

(4 posts)
  • Started 10 months ago by keyworks
  • Latest reply from AutoSponge
  1. keyworks
    Member

    How can I write a VBA macro in Excel, or use some other automated programming tool to pick up the original client-side file creation date and author on the client machine? I want to substitute that date in the document library when a file is uploaded. I have that information listed in an Excel spreadsheet already, with a full path to the file included on the same row, so excel would be the easiest method.

    As it is right now, when users drag and drop files using Explorer View or any other standard method, the file creation date of the original file is replaced by the current date. I don't want to require manual input for the correct dates, or the users will never move the masses of files that we are talking about, only to lose this data. I want this tool to be available through Excel or some other method that does not require designer privileges on the site for end users who want to upload.

    Is this possible without writing new server-side code?

    PS government client will not purchase add-on commercial products but they might install free customized server-side programs or web-parts if they can review the code

    Posted 10 months ago #
  2. I think the common solution is a console application.

    You write a C# application that runs client side and talks to MOSS through the API or Web Service to input data. I've seen it done more for those one-time conversions.

    Even then, you may need to use a custom web service if you want fields updated that are not usually available (like created). There's some example code here:
    http://www.eggheadcafe.com/software/aspnet/29904945/change-modificationcreat.aspx

    Posted 10 months ago #
  3. keyworks
    Member

    Thanks, but this doesnt solve my problem since I am looking for client-side solutions. I cant install custom web services. Any other answers are still appreciated, especially any hints on how VBA might be employed rather than C#.

    Posted 9 months ago #
  4. I guess I wasn't clear. A console application in C# is a client-side application and it would talk to the built-in MOSS web services or API. You only need custom server-side code if you need to change data in MOSS that the OOB web services do not offer. I haven't done any VBA in years, but I'm sure someone has a way to talk web services with VBA which is probably your only option.

    Posted 9 months ago #

RSS feed for this topic

Reply

You must log in to post.