Index Server Script issue: VPATH is not returning anything

Discussion:

(too old to reply)

MikeD

2006-11-10 20:18:02 UTC

I can display the path but not vpath.
I tried
Response.write "VPath: " & oRS("Vpath") & " "

in never works on me.

Also on my catalog\directories, the icon is a folder icon and not a globe
icon. How can I make it to show globe icon so that VPATH will display?

Hilary Cotter

2006-11-10 22:18:05 UTC

Permalink

locate the folder in file explorer, right click on it and select sharing and
security, and then web sharing. Select share this folder, and Park the
directory in your default web site.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

Post by MikeD
I can display the path but not vpath.
I tried
Response.write "VPath: " & oRS("Vpath") & " "
in never works on me.
Also on my catalog\directories, the icon is a folder icon and not a globe
icon. How can I make it to show globe icon so that VPATH will display?

Alec MacLean

2007-01-18 14:42:12 UTC

Permalink

Mike,

I have found that I cannot include both VPath and URL in the same result
set. If both are included in the select, only the one that is last in the
qery statement will be returned. The same might be occuring for "path".

For example:

SELECT Filename, url, VPath from SCOPE() ...

will return just filename and VPath, whereas

SELECT Filename, VPath, url from SCOPE() ...

will return just filename and url.

Strangely, it doesn't fail on the query, but only when trying to bind the
results to the display column. So if the datagridview doesn't include a
reference to the non-returned column, the rest of the statement still seems
to operate OK.

This would indicate that the query syntax isn't at fault (at least
strictly), but that something internal to the Index Server producing the
results doesn't allow both to be returned.

Anyone else notice this?

Al