Hello again:<BR><BR>I am trying to list what needs to be done to migrate from interpreted VBScript in ASP to compiled VB in ASPX. <BR><BR>Could it be as simple as this? I apologize in advance for my incomplete knowledge of Visual Basic.<BR><BR><BR>ASP: filename.asp<BR>ASPX: filename.aspx<BR><BR>ASP: &#060;% &#039 run-time engine will interpret as VBScript <BR>ASPX: &#060;% &#039 run-time engine will compile as VB 7.0<BR><BR>ASP: %&#062; <BR>ASPX: %&#062;<BR><BR>ASP: dim var_name<BR>ASPX: dim var_name &#039 will be compiled to variant?<BR>ASPX: dim var_name as &#060;type&#062; &#039 is that needed for a non-variant?<BR><BR>ASP: Set obj_name = CreateObject("myobject")<BR>ASPX: obj_name = CreateObject("myobject") <BR>&#039 I heard you dont need set or get in VB7, is that correct?<BR><BR>ASP: SubroutineName arg1, arg2 , arg3<BR>ASPX: SubroutineName(arg1, arg2, arg3)<BR>&#039 You always need parenthesis after a function or sub call.<BR><BR>ASP: eval() and execute()<BR>ASPX: not available.<BR><BR>ASP: Timer()<BR>ASPX: ??? &#039 is that function available?<BR><BR>ASP: &#039 no sleep function available<BR>ASPX: sleep() &#039 very useful to stop this page thread<BR><BR>ASP: Server, Request and Response objects<BR>ASPX: &#039 I think the objects are still there with the same API.<BR><BR>ASP: Application, Session<BR>ASPX: &#039 what about these, and their API?<BR><BR>ASP: Variables named like aspx.* objects, e.g, Page or Error<BR>ASPX: You need to rename them, e.g., to myPage and myError.<BR><BR><BR><BR><BR>Giovanni<BR><BR>PS Thank you very much to Doug Seven for his reply to my <BR>RE: Could aspx.page object conflict with a variable named "Page".<BR><BR>