You can use Application.Version and IF/THEN logic re OpenText:

If Val(Application.Version) 9 Then
...OpenText with TrailingMinus
Else
...OpenText without TrailingMinus
End If

With regard to CreateObject("Scripting.FileSystemObject") I'd first ask why
you're using it. It may be possible to replace it with something that works
under WinNT. If not you have to tell users they can't run your app by using
error trapping:

On Error Goto BadOS
Set fso = CreateObject("Scripting.FileSystemObject")
...other stuff
Exit Sub
BadOS:
Msgbox "You need scripting"
End Sub


--
Jim
"John Keith" wrote in message
...
|I am having fits trying to deploy a spreadsheet with VBA.
|
| I have developed the sheet in Excel2002-SP3(loaded from XP Office prof
2003)
| on Windows2000 SP4
| It works fine on that platform...
| it also works on a Win2000 SP2 platform.
|
| On a NT based PC runing Excel2000 this line gives a compile error:
| Set fso = CreateObject("Scripting.FileSystemObject")
|
| On win2000 running Excel2002-sp1...
| Complie error on the "TrailingMinusNumbers:=True" of the Workbook.OpenText
| cmd. Removed that option completely (since its optional anyway) and then
the
| macro runs up to the OpenText command then it gets a "Runtime error 1004:
| Method OpenText of object Workbooks failed" note: the FileSystemObject
| statement above executed fine on this one.
|
| How can I code these statements so that they are version independent? Or
| have logic that will detect the environment and only run the statements
that
| will work.
|
| --
| Regards,
| John