Alternative to using a DLL

[Cheitan]

Picture this:
New job, started two weeks ago for the summer. They give me a project. For two weeks, I work on it. It's an ASP project.

Now I needed to do a DLL you see, otherwise I would have to copy about 100lines of code on every page that uses that code (Over 30), and it was just plain crazy because the slightest change I had to do would have to be done on the 30 pages. So after two weeks, I manage to get everything working, with the DLL.

Now, luck has it on my side. No, wait... It doesn't!

I go tell my boss I'm finished, show him the final work, everything is fine exept one this: It uses a DLL, and the server is in Ottawa, we in Montreal, and therefor we don't have access to register the DLL.

So I need an alternative to this, and theres no way I'll give in to copying the code on the 30 pages, it would just be a bloody mess of code! Unless of course, I have to.

Global.x wouldn't work, would it? It's too limited. Anything else?

Can anybody help?

[JoshT]

Use Server Side Includes, or if you're running Windows 2000, Server.Execute.

[Cheitan]

I have absolutely NO access to the server. We have a directory on the server, that's all.

I'm not sure I understand exactly what you mean, can you explain?

[eL_NiNo]

Yeah, why don't you use "include" ?
This, way you just put your asp code in a file and then include it in each page. It'S only a line and it works pretty well...

Example of include call in asp page :

<!--#include file="functions.inc"-->

and the file looks like this :

<%
function One()
end function

sub one()
end sub

... you get the point
%>

Hope this helps !

[Cheitan]

eL_NiNo: Thanks a lot, that's exactly what I used and it works like a charm. Thanks again!

[Cheitan]

eL_NiNo: Thanks a lot, that's exactly what I used and it works like a charm. Thanks again!