in reply to Dynamic Web Page approach?

Use .NET, particularly VBA, on top of IIS. Not only will VBA have all the functions you need to handle this, but, since you're running on Win32, you might as well use IIS. And, you have a ton of prior art to work from.

As for LAMP, Apache suffers from problems on Win32, Perl doesn't talk to Access that well, and you're not using Linux or MySQL.

In other words, use the right tool for the job. In this case, Perl isn't it.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^2: Dynamic Web Page approach?
by Herkum (Parson) on Apr 10, 2006 at 18:19 UTC

    I think a better question to ask was why was he looking at Perl? He said that he had not looked in Perl in a while and he had no constraints on how to implement it.

    My question would be, are you trying Perl to learn something or do you just want find a tool to get the job down quickly?

    Do you even have a Windows server to with? What platforms do you have access too?

[reply]
      I use perl daily (Activestate 5.8 mostly) for a variety of system administration and configuration management tasks and I use it extensively in ClearQuest and ClearCase (stupid bad rational's perl's) to customize those application's behavior, generating reports and other tasks including some html reports, hooks, triggers.

      Having done extracts from Access using perl to load ClearQuest database using the CQ API and WIN32::OLE it didn't seem far fetched to use Access as the database for this. My guess is that we could just as easily use mysql. I'm familiar with Access and it's a quick tool for prototyping the database so that's where I started.

      Why perl? I'd like to continue to extend my perl skills (practice makes...er...well anyway...) and I use them whenever I can, I enjoy it. It is unlikely I'll ever be able to become a truly competent perl developer without continuing to exercise it. I'd also rather go with the devil...er..language I know rather than the language I don't know (ie. VB.NET).

      I'm still trying to identify what the hosting platform is for this project. I personally have access to a linux box (RH9) at home and more XP boxes than are really necessary. This is a "extra-curricular" project aimed at satisfying a quarterly MBO objective vaguely titled "build the company" or something equally obscure. The company is small and young. A fair questions is do they know what they're doing? Why was this assigned to me? Because I was available and asked for it. If they had to pay a FTE for this it could be many months before they'd get the work done. gj

[reply]
        I'd have to recomend against Access. Do you really want Office installed on a server? Did you know Outlook and Exhcange cannot reside on the same server? Could there be other comptibility isues you may run into later on (e.g. what if they want to put SQL Server on there later on)? Do you want to have to upgrade it at Microsft's whim or lose security patches, etc? If you are using Microsoft Update then it will want to update Access as well. And what happens when the project outgrows Access? You are better off picking MySQL or Postgres-SQL from the get go. My US$0.02 anyway.
[reply]

In Section Seekers of Perl Wisdom