Is Lisp Microsoft Sharepoint compatible

[prose]

Our Company is switching over to use Microsoft Sharepoint.
One of the IT guys asked if AutoCAD could read the lisp files out of a database, that way, they can incorporate the lisp files on the server into MS Sharepoint.
Does anyone know if this would be possible?

[mweaver]

Our Company is switching over to use Microsoft Sharepoint.
One of the IT guys asked if AutoCAD could read the lisp files out of a database, that way, they can incorporate the lisp files on the server into MS Sharepoint.
Does anyone know if this would be possible?

I suppose lisp code could be stored in a database text field. Then a lisp routine could read that database field and execute the code. This would require one base lisp file be loaded prior to accessing the database.

That said. Why? What is gained by putting the lisp on sharepoint?

Mike

[prose]

I suppose lisp code could be stored in a database text field. Then a lisp routine could read that database field and execute the code. This would require one base lisp file be loaded prior to accessing the database.

That said. Why? What is gained by putting the lisp on sharepoint?

Mike

Not quite sure. All I know is they are wanting to move everything they can over to Sharepoint. It may just be something I will have to say no, not going to work.

[RobertB]

Unrelated:
Drawings with XRefs will be an issue.
Sheet Sets/Project Navigator will be an issue.
There are probably a whole host of other issues.

At the moment, AutoCAD is best served <groan> by the traditional server environment.

[prose]

Unrelated:
Drawings with XRefs will be an issue.
Sheet Sets/Project Navigator will be an issue.
There are probably a whole host of other issues.

At the moment, AutoCAD is best served <groan> by the traditional server environment.

Thanks for that. I just need something to back up my answer of "Yes" or "No" on whether I want it on SharePoint.

It seems my answer will be no, and I will use your guys response to help support my answer. Thanks again.

Once again AUGI saves the day. ;)

[irneb]

The prob is AC needs to read various files at once, not just the one DWG you're opening. As RobertB's stated there's a huge amount of other stuff that would also cause problems on a Database Server (Like Share Point).

For LSP it may, or may not give problems ... depending on how your particular customization is set up. Off the top of my head:

Custom MNU or CUI files may have related MNL lisp, and even MNR.
Some lisp routines would require others to be loaded, and would then try loading them through a (load "filename") call ... which would fail ... so you need to change all these calls to 1st get the string from the DB & then read.
What happens with stuff like DCL for custom dialog boxes? Those are also quite difficult to load from a DB.The only way I can see to make sure your lisp works is to compile it to VLX and include all DCL and other LSP files which may be used in each VLX. Obviously, this would probably cause quite a lot of duplication. And also I'm unsure if a simple text field in a database would work with a VLX ... since it's binary compiled code. :?