MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Importing a spreadsheet to create a list in WSS 3.0 fails when using

  Asked By: Mercedes    Date: Apr 02    Category: MOSS    Views: 2454

I have a test WSS 3.0 site. I tried creating a list using import from a
spreadsheet. I first tried it on a workstation that had Excel 2003 on
it, loading an Excel 2003 file. The import failed with an error message
about a missing object or method. I then tried the same process from a
workstation with Excel 2007, loading an Excel 2007 file. It succeeded.
Is there any way to make this work from Excel 2003? We are planning to
roll out WSS 3.0 before we roll out Office 2007, but this glitch makes
me worry there are other incompatibilities between WSS 3.0 and Office



2 Answers Found

Answer #1    Answered By: Carey Everett     Answered On: Apr 02

We also imported a list  in 2007 and we had this problem so we had to fix it
in back end and we were able to import  list.

Go to c:\program Files\Microsoft Office\Office12\1033-EXPTOOWS.XLA

Open this file and fix this function

Comment this line<< 'lVer = Application.SharePointVersion(URL) '>>

Iver = 2

So your function should look like this


Sub Initialize(List, Title, URL, QuickLaunch)

strQuickLaunch = QuickLaunch

aTarget(iPublishURL) = URL

aTarget(iPublishListName) = List

aTarget(iPublishListDesc) = Title

'lVer = Application.SharePointVersion(URL) '

lVer = 2

End Sub

After changing this file we were able to import list. Hope it helps you.

Answer #2    Answered By: Anuj Lakhe     Answered On: Apr 02

I have two follow-up questions:

1. On my server, there seems to be a file like the one you mention,
but it is in C:\program files\microsoft office\office12\1033\ and it
is called EXPTOOWS.XLA. Is this the same file as the one you mention?
It seems to have the same content. I found the function you refer to
in it.

2. The XLA file on my server is digitally signed by Microsoft. How do
you make changes to a file that is digitally signed by Microsoft? As
soon as you do, it will no longer be digitally signed. Won't that
lead to error messages when the client tries to use it?