File Reference Problem

Yahoo Archive
1
Yeah. I didn't say that I've *replaced* the drive letters with the
DFS one.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Tony Hughes
Sent: Friday, March 06, 2009 11:47 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: File Reference Problem



That would be too simple, users would never be able to handle that.

User: hey, I don't have the T: drive mapped anymore, I just have K, the
Quality drive.
IT: yes, just open K:, look for your Engineering folder
User: well, that's not the right one. I don't know what is in that
engineering folder showing in K: but our folder is in T:
IT: no, it's same files as always.
User: but, K: is where Quality puts their documents, we're Engineering,
we use T:
IT: <pulls hair out> T: no longer exists, what was in T: is now in K:
User: Why did you move the files in T over to K? K is for Quality, we
need to move them back to the T: Drive...
IT: <drinks heavily>

see where this is going? hahaha

________________________________
From: Brian W. Spolarich <bspolarich@...
<mailto:bspolarich%40advancedphotonix.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Friday, March 6, 2009 10:40:54 AM
Subject: RE: [Vantage] Re: File Reference Problem

Windows DFS can also help you with this. You can actually just have a
single drive letter, and map all of your shares into a DFS hierarchy
that's the same for everyone in your AD domain.

It works well and can avoid the drive letter madness.

-bws

--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@advanced photonix. com ~ 734-864-5618 ~
www.advancedphotoni x.com

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On
Behalf
Of Tony Hughes
Sent: Friday, March 06, 2009 11:36 AM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Re: File Reference Problem

I agree.
only letter on our network that is different for each user is U: which
maps to their home directory.
T: or K: or whatever needs to be identical for all users, regardless.

____________ _________ _________ __
From: rob.bucek <rob.bucek@yahoo. com <mailto:rob. bucek%40yahoo. com> >
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Sent: Friday, March 6, 2009 9:23:48 AM
Subject: [Vantage] Re: File Reference Problem

Im a root cause guy, i think you need to start by having a central file
server (pick one any one) and make sure that anyone creating electonic
documents that are referenced by others in your company stores them in
your file server. All our drawings, customer specifications, ISO docs,
engineering files (cad) are on one computer/server. Permisions to
individual folders on that drive may vary of course depending on the
nature of what is being stored there. Accessability to information is
key as you are indicating, not having a comprehensive policy on public
company documents is causing you to have to create this work around.
Just my two cents--- In vantage@yahoogroups .com, "Charlie Wilson"
<foamdesigncsw@ ...> wrote:
>
> All,
>
>
>
> We often use the feature that allows you to "attach" files to
different
> vantage documents such as job methods and orders for purposes of
attaching
> drawings and certification paper work. The only problem with this
feature is
> that the file isn't actually uploaded to the Vantage database instead
I
> record is created with a link to the file where ever it may be. Now I
> understand that this was done to reduce the size of the database but
this
> causes all sorts of problems further down the road.
>
>
>
> One of the problems we are trying to over come is many people for my
company
> have network shares mapped to drive letters on their computer for
example
> share \\fileserv1\ common <file:/// <file:///\\> <file:///
<file:///\\> \\> \\fileserv1\ common>
is mapped to the Z:
> drive. Now when you "attach" a file from this mapped drive vantage
picks up
> the files location as z:\file.txt. the problem this causes is that not
every
> single person has the same drive mappings to when another person
attempts to
> open the file they may get a file not found error because on their
machine
> \\fileserv1\ common <file:/// <file:///\\> <file:/// <file:///\\> \\>
\\fileserv1\ common> is
mapped to Y:. So is
> there a way to make vantage detect this absolute mapping so that it
creates
> the record \\fileserv1\ common\file. txt <file:/// <file:///\\>
<file:/// <file:///\\> \\>
\\fileserv1\ common\file. txt>
> instead of z:\file.txt.
>
>
>
> I'm also left with the problem of fixing the 2400 files that have
already
> been "attached". To do this I attempted copying all the info out to an
excel
> file and doing a find and replace to fix what I could and then
attempting to
> do a paste update to put all the changes back in from the external
file
> reference app. The problem with this is that when it get to the bottom
of
> the file references that can fit on one screen and it begins to scroll
I get
> a Update could not be completed error message. Any ideas on how to get
past
> this?
>
>
>
> ~Charlie
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
2
All,



We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.



One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:///\\fileserv1\common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:///\\fileserv1\common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:///\\fileserv1\common\file.txt>
instead of z:\file.txt.



I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?



~Charlie



[Non-text portions of this message have been removed]
3
Charlie,
You can use the ip address of the computer or server instead - ie: \\168.2.x.xxx\common\filename when you attach the document.

Hope that helps!
Julie
Mercury Minnesota Inc.




----- Original Message -----
From: Charlie Wilson
To: vantage@yahoogroups.com
Sent: Friday, March 06, 2009 7:13 AM
Subject: [Vantage] File Reference Problem


All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:///\\fileserv1\common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:///\\fileserv1\common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:///\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
4
That got messed up when I sent it in. the problem isn't the server name it's
the fact that they have shares mapped to drive letters and vantage picks up
this drive letter instead of the server name and share name.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Julie Lehmann
Sent: Friday, March 06, 2009 8:29 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] File Reference Problem



Charlie,
You can use the ip address of the computer or server instead - ie:
\\168.2.x.xxx\common\filename when you attach the document.

Hope that helps!
Julie
Mercury Minnesota Inc.

----- Original Message -----
From: Charlie Wilson
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Friday, March 06, 2009 7:13 AM
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:/// <file:///\\> \\fileserv1\common> is
mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:/// <file:///\\> \\fileserv1\common> is mapped to
Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:/// <file:///\\>
\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 02/27/09
13:27:00




[Non-text portions of this message have been removed]
5
Funny thing, we just had this same discussion here yesterday, but in reverse. All our CAD file references are in UNC format with the server name but we are going to change servers soon with a different name. All the \\xtore\<file://\\xtore\>... references will be \\vault1\<file://\\vault1\>... It would have been much easier if we had used a mapped drive letter. Of course as you point out consistancy across all the users would be mandatory. We discussed directly updating the data in Vantage via ODBC and an Access update query but this would require more investigation to assure that there are no other references in the DB.
-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups.com
Subject: [Vantage] File Reference Problem


All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:///\\fileserv1\common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:///\\fileserv1\common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:///\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
6
We partially solve the whole problem by designating our regular file server as drive S:. Everyone, in spite of the fact that they are PERSONAL computers, has drive S: mapped to the server. When we migrated our server last year, files saved as S:\... were still retrievable because everyone changed their S: map to the new server, and all the file structures were otherwise identical. BTW, we also have everyone map the Epicor server as E:. To keep some "personality" in the personal computers, we allow users to map all their other drives as they wish. However, anyone who wants to add an attachment, needs to start at S:\ and include the rest of the file structure to where the file resides.

Thom Rose
Controller
Electric Mirror LLC
HOTEL LUXURY

"The World Leader in Back-lit Mirrors & Mirror TV Technology"

T 425 776-4946
F 425 491-8200
A 11831 Beverly Park Rd, Bldg D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com>

Note: The information contained in the e-mail, including any attachments, is legally privileged and confidential. If you are not the intended recipient you are hereby notified that any reading, use or dissemination of this message is strictly prohibited. If you have received this message in error, please immediately notify us by telephone at 425-776-4946 and delete this message from your system. Even though this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free, and no responsibility is accepted by Electric Mirror LLC for any loss or damage arising in any way from its use


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Todd Caughey
Sent: Friday, March 06, 2009 6:07 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] File Reference Problem


Funny thing, we just had this same discussion here yesterday, but in reverse. All our CAD file references are in UNC format with the server name but we are going to change servers soon with a different name. All the \\xtore\<file://\\xtore\>... references will be \\vault1\<file://\\vault1\>... It would have been much easier if we had used a mapped drive letter. Of course as you point out consistancy across all the users would be mandatory. We discussed directly updating the data in Vantage via ODBC and an Access update query but this would require more investigation to assure that there are no other references in the DB.
-Todd C.

________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:///<file:///\\>\\fileserv1\common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:///<file:///\\>\\fileserv1\common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:///<file:///\\>\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
7
You can easily update them from the external file reference app it will let
you change that mapping all day long, everything in vantage uses that
reference number so you can change the path when ever you want you just
can't delete the record. The problem is we have about 140 users and 1 me so
it's hard to keep all the drive letters locked down especially since we have
multiple locations with their own file share and of course each location
maps share basically how ever they please..



If you change it to use the server name\share name it would be independent
of those drive mappings and nothing would really stop you from opening the
file.



This was a major design flaw in my opinion the file should be sucked into
the DB or copied to an independent location that is then referenced by the
vantage server.



We are planning to write a SC flow to fix the ones already there, and doing
something else to combat the future attachments. The only problem is unless
I can find a way to detect what they have that mapping connected to I have
to just assume z: is this and y: is that. Which really isn't that good.





~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Todd Caughey
Sent: Friday, March 06, 2009 9:07 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] File Reference Problem



Funny thing, we just had this same discussion here yesterday, but in
reverse. All our CAD file references are in UNC format with the server name
but we are going to change servers soon with a different name. All the
\\xtore\<file://\\xtore\>... references will be
\\vault1\<file://\\vault1\>... It would have been much easier if we had used
a mapped drive letter. Of course as you point out consistancy across all the
users would be mandatory. We discussed directly updating the data in Vantage
via ODBC and an Access update query but this would require more
investigation to assure that there are no other references in the DB.
-Todd C.

________________________________
From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:/// <file:///\\> \\fileserv1\common> is
mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:/// <file:///\\> \\fileserv1\common> is mapped to
Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:/// <file:///\\>
\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 02/27/09
13:27:00




[Non-text portions of this message have been removed]
8
We have about 20 some odd shares a server and some people don't have
permissions to certain shares.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Thomas Rose
Sent: Friday, March 06, 2009 9:15 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] File Reference Problem



We partially solve the whole problem by designating our regular file server
as drive S:. Everyone, in spite of the fact that they are PERSONAL
computers, has drive S: mapped to the server. When we migrated our server
last year, files saved as S:\... were still retrievable because everyone
changed their S: map to the new server, and all the file structures were
otherwise identical. BTW, we also have everyone map the Epicor server as E:.
To keep some "personality" in the personal computers, we allow users to map
all their other drives as they wish. However, anyone who wants to add an
attachment, needs to start at S:\ and include the rest of the file structure
to where the file resides.

Thom Rose
Controller
Electric Mirror LLC
HOTEL LUXURY

"The World Leader in Back-lit Mirrors & Mirror TV Technology"

T 425 776-4946
F 425 491-8200
A 11831 Beverly Park Rd, Bldg D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electric <http://www.electricmirror.com>
mirror.com>

Note: The information contained in the e-mail, including any attachments, is
legally privileged and confidential. If you are not the intended recipient
you are hereby notified that any reading, use or dissemination of this
message is strictly prohibited. If you have received this message in error,
please immediately notify us by telephone at 425-776-4946 and delete this
message from your system. Even though this e-mail and any attachments are
believed to be free of any virus or other defect that might affect any
computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free, and no
responsibility is accepted by Electric Mirror LLC for any loss or damage
arising in any way from its use

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Todd Caughey
Sent: Friday, March 06, 2009 6:07 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: [Vantage] File Reference Problem

Funny thing, we just had this same discussion here yesterday, but in
reverse. All our CAD file references are in UNC format with the server name
but we are going to change servers soon with a different name. All the
\\xtore\<file://\\xtore\>... references will be
\\vault1\<file://\\vault1\>... It would have been much easier if we had used
a mapped drive letter. Of course as you point out consistancy across all the
users would be mandatory. We discussed directly updating the data in Vantage
via ODBC and an Access update query but this would require more
investigation to assure that there are no other references in the DB.
-Todd C.

________________________________
From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com<mailto:vantage%40yahoogroups.com>]
On Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\common <file:/// <file:///\\> <file:/// <file:///\\>
\\>\\fileserv1\common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\common <file:/// <file:///\\> <file:/// <file:///\\>
\\>\\fileserv1\common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\common\file.txt <file:/// <file:///\\> <file:///
<file:///\\> \\>\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date: 02/27/09
13:27:00




[Non-text portions of this message have been removed]
9
I have used SQL UPDATE statements on xfileref.xfilename (the table.field holding the full path of the attached files) many, many times and have never experienced any problems, if this helps people at all.

8.03.406, SQL version. (although, it has been all different versions of 8.x while I've been doing it)







________________________________
From: Thomas Rose <t.rose@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Friday, March 6, 2009 8:15:04 AM
Subject: RE: [Vantage] File Reference Problem


We partially solve the whole problem by designating our regular file server as drive S:. Everyone, in spite of the fact that they are PERSONAL computers, has drive S: mapped to the server. When we migrated our server last year, files saved as S:\... were still retrievable because everyone changed their S: map to the new server, and all the file structures were otherwise identical. BTW, we also have everyone map the Epicor server as E:. To keep some "personality" in the personal computers, we allow users to map all their other drives as they wish. However, anyone who wants to add an attachment, needs to start at S:\ and include the rest of the file structure to where the file resides.

Thom Rose
Controller
Electric Mirror LLC
HOTEL LUXURY

"The World Leader in Back-lit Mirrors & Mirror TV Technology"

T 425 776-4946
F 425 491-8200
A 11831 Beverly Park Rd, Bldg D, Everett, WA 98204 USA
www.electricmirror. com<http://www.electric mirror.com>

Note: The information contained in the e-mail, including any attachments, is legally privileged and confidential. If you are not the intended recipient you are hereby notified that any reading, use or dissemination of this message is strictly prohibited. If you have received this message in error, please immediately notify us by telephone at 425-776-4946 and delete this message from your system. Even though this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free, and no responsibility is accepted by Electric Mirror LLC for any loss or damage arising in any way from its use

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf Of Todd Caughey
Sent: Friday, March 06, 2009 6:07 AM
To: vantage@yahoogroups .com
Subject: RE: [Vantage] File Reference Problem

Funny thing, we just had this same discussion here yesterday, but in reverse. All our CAD file references are in UNC format with the server name but we are going to change servers soon with a different name. All the \\xtore\<file: //\\xtore\ >... references will be \\vault1\<file: //\\vault1\ >... It would have been much easier if we had used a mapped drive letter. Of course as you point out consistancy across all the users would be mandatory. We discussed directly updating the data in Vantage via ODBC and an Access update query but this would require more investigation to assure that there are no other references in the DB.
-Todd C.

____________ _________ _________ __
From: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com> [mailto:vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>] On Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups .com<mailto:vantage% 40yahoogroups. com>
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of attaching
drawings and certification paper work. The only problem with this feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my company
have network shares mapped to drive letters on their computer for example
share \\fileserv1\ common <file:///<file:///\\>\\fileserv1\ common> is mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks up
the files location as z:\file.txt. the problem this causes is that not every
single person has the same drive mappings to when another person attempts to
open the file they may get a file not found error because on their machine
\\fileserv1\ common <file:///<file:///\\>\\fileserv1\ common> is mapped to Y:. So is
there a way to make vantage detect this absolute mapping so that it creates
the record \\fileserv1\ common\file. txt <file:///<file:///\\>\\fileserv1\ common\file. txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have already
been "attached". To do this I attempted copying all the info out to an excel
file and doing a find and replace to fix what I could and then attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom of
the file references that can fit on one screen and it begins to scroll I get
a Update could not be completed error message. Any ideas on how to get past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
10
We use group policy and a logon script so every user has the same half
dozen or so mapped drives no matter where they are or what machine they
log on to.



Mark D



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Friday, March 06, 2009 9:25 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] File Reference Problem



You can easily update them from the external file reference app it will
let
you change that mapping all day long, everything in vantage uses that
reference number so you can change the path when ever you want you just
can't delete the record. The problem is we have about 140 users and 1 me
so
it's hard to keep all the drive letters locked down especially since we
have
multiple locations with their own file share and of course each location
maps share basically how ever they please..

If you change it to use the server name\share name it would be
independent
of those drive mappings and nothing would really stop you from opening
the
file.

This was a major design flaw in my opinion the file should be sucked
into
the DB or copied to an independent location that is then referenced by
the
vantage server.

We are planning to write a SC flow to fix the ones already there, and
doing
something else to combat the future attachments. The only problem is
unless
I can find a way to detect what they have that mapping connected to I
have
to just assume z: is this and y: is that. Which really isn't that good.

~Charlie

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Todd Caughey
Sent: Friday, March 06, 2009 9:07 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] File Reference Problem

Funny thing, we just had this same discussion here yesterday, but in
reverse. All our CAD file references are in UNC format with the server
name
but we are going to change servers soon with a different name. All the
\\xtore\<file://\\xtore\>... references will be
\\vault1\<file://\\vault1\>... It would have been much easier if we had
used
a mapped drive letter. Of course as you point out consistancy across all
the
users would be mandatory. We discussed directly updating the data in
Vantage
via ODBC and an Access update query but this would require more
investigation to assure that there are no other references in the DB.
-Todd C.

________________________________
From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Charlie Wilson
Sent: Friday, March 06, 2009 7:14 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: [Vantage] File Reference Problem

All,

We often use the feature that allows you to "attach" files to different
vantage documents such as job methods and orders for purposes of
attaching
drawings and certification paper work. The only problem with this
feature is
that the file isn't actually uploaded to the Vantage database instead I
record is created with a link to the file where ever it may be. Now I
understand that this was done to reduce the size of the database but
this
causes all sorts of problems further down the road.

One of the problems we are trying to over come is many people for my
company
have network shares mapped to drive letters on their computer for
example
share \\fileserv1\common <file:/// <file:///\\> <file:/// <file:///\\>
\\> \\fileserv1\common> is
mapped to the Z:
drive. Now when you "attach" a file from this mapped drive vantage picks
up
the files location as z:\file.txt. the problem this causes is that not
every
single person has the same drive mappings to when another person
attempts to
open the file they may get a file not found error because on their
machine
\\fileserv1\common <file:/// <file:///\\> <file:/// <file:///\\> \\>
\\fileserv1\common> is mapped to
Y:. So is
there a way to make vantage detect this absolute mapping so that it
creates
the record \\fileserv1\common\file.txt <file:/// <file:///\\> <file:///
<file:///\\> \\>
\\fileserv1\common\file.txt>
instead of z:\file.txt.

I'm also left with the problem of fixing the 2400 files that have
already
been "attached". To do this I attempted copying all the info out to an
excel
file and doing a find and replace to fix what I could and then
attempting to
do a paste update to put all the changes back in from the external file
reference app. The problem with this is that when it get to the bottom
of
the file references that can fit on one screen and it begins to scroll I
get
a Update could not be completed error message. Any ideas on how to get
past
this?

~Charlie

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.4/1976 - Release Date:
02/27/09
13:27:00

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
11
Im a root cause guy, i think you need to start by having a central file server (pick one any one) and make sure that anyone creating electonic documents that are referenced by others in your company stores them in your file server. All our drawings, customer specifications, ISO docs, engineering files (cad) are on one computer/server. Permisions to individual folders on that drive may vary of course depending on the nature of what is being stored there. Accessability to information is key as you are indicating, not having a comprehensive policy on public company documents is causing you to have to create this work around. Just my two cents--- In vantage@yahoogroups.com, "Charlie Wilson" <foamdesigncsw@...> wrote:
>
> All,
>
>
>
> We often use the feature that allows you to "attach" files to different
> vantage documents such as job methods and orders for purposes of attaching
> drawings and certification paper work. The only problem with this feature is
> that the file isn't actually uploaded to the Vantage database instead I
> record is created with a link to the file where ever it may be. Now I
> understand that this was done to reduce the size of the database but this
> causes all sorts of problems further down the road.
>
>
>
> One of the problems we are trying to over come is many people for my company
> have network shares mapped to drive letters on their computer for example
> share \\fileserv1\common <file:///\\fileserv1\common> is mapped to the Z:
> drive. Now when you "attach" a file from this mapped drive vantage picks up
> the files location as z:\file.txt. the problem this causes is that not every
> single person has the same drive mappings to when another person attempts to
> open the file they may get a file not found error because on their machine
> \\fileserv1\common <file:///\\fileserv1\common> is mapped to Y:. So is
> there a way to make vantage detect this absolute mapping so that it creates
> the record \\fileserv1\common\file.txt <file:///\\fileserv1\common\file.txt>
> instead of z:\file.txt.
>
>
>
> I'm also left with the problem of fixing the 2400 files that have already
> been "attached". To do this I attempted copying all the info out to an excel
> file and doing a find and replace to fix what I could and then attempting to
> do a paste update to put all the changes back in from the external file
> reference app. The problem with this is that when it get to the bottom of
> the file references that can fit on one screen and it begins to scroll I get
> a Update could not be completed error message. Any ideas on how to get past
> this?
>
>
>
> ~Charlie
>
>
>
> [Non-text portions of this message have been removed]
>
12
I agree.
only letter on our network that is different for each user is U: which maps to their home directory.
T: or K: or whatever needs to be identical for all users, regardless.




________________________________
From: rob.bucek <rob.bucek@...>
To: vantage@yahoogroups.com
Sent: Friday, March 6, 2009 9:23:48 AM
Subject: [Vantage] Re: File Reference Problem


Im a root cause guy, i think you need to start by having a central file server (pick one any one) and make sure that anyone creating electonic documents that are referenced by others in your company stores them in your file server. All our drawings, customer specifications, ISO docs, engineering files (cad) are on one computer/server. Permisions to individual folders on that drive may vary of course depending on the nature of what is being stored there. Accessability to information is key as you are indicating, not having a comprehensive policy on public company documents is causing you to have to create this work around. Just my two cents--- In vantage@yahoogroups .com, "Charlie Wilson" <foamdesigncsw@ ...> wrote:
>
> All,
>
>
>
> We often use the feature that allows you to "attach" files to different
> vantage documents such as job methods and orders for purposes of attaching
> drawings and certification paper work. The only problem with this feature is
> that the file isn't actually uploaded to the Vantage database instead I
> record is created with a link to the file where ever it may be. Now I
> understand that this was done to reduce the size of the database but this
> causes all sorts of problems further down the road.
>
>
>
> One of the problems we are trying to over come is many people for my company
> have network shares mapped to drive letters on their computer for example
> share \\fileserv1\ common <file:///\\fileserv1\ common> is mapped to the Z:
> drive. Now when you "attach" a file from this mapped drive vantage picks up
> the files location as z:\file.txt. the problem this causes is that not every
> single person has the same drive mappings to when another person attempts to
> open the file they may get a file not found error because on their machine
> \\fileserv1\ common <file:///\\fileserv1\ common> is mapped to Y:. So is
> there a way to make vantage detect this absolute mapping so that it creates
> the record \\fileserv1\ common\file. txt <file:///\\fileserv1\ common\file. txt>
> instead of z:\file.txt.
>
>
>
> I'm also left with the problem of fixing the 2400 files that have already
> been "attached". To do this I attempted copying all the info out to an excel
> file and doing a find and replace to fix what I could and then attempting to
> do a paste update to put all the changes back in from the external file
> reference app. The problem with this is that when it get to the bottom of
> the file references that can fit on one screen and it begins to scroll I get
> a Update could not be completed error message. Any ideas on how to get past
> this?
>
>
>
> ~Charlie
>
>
>
> [Non-text portions of this message have been removed]
>







[Non-text portions of this message have been removed]
13
Windows DFS can also help you with this. You can actually just have a
single drive letter, and map all of your shares into a DFS hierarchy
that's the same for everyone in your AD domain.



It works well and can avoid the drive letter madness.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Tony Hughes
Sent: Friday, March 06, 2009 11:36 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Re: File Reference Problem



I agree.
only letter on our network that is different for each user is U: which
maps to their home directory.
T: or K: or whatever needs to be identical for all users, regardless.

________________________________
From: rob.bucek <rob.bucek@... <mailto:rob.bucek%40yahoo.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Friday, March 6, 2009 9:23:48 AM
Subject: [Vantage] Re: File Reference Problem

Im a root cause guy, i think you need to start by having a central file
server (pick one any one) and make sure that anyone creating electonic
documents that are referenced by others in your company stores them in
your file server. All our drawings, customer specifications, ISO docs,
engineering files (cad) are on one computer/server. Permisions to
individual folders on that drive may vary of course depending on the
nature of what is being stored there. Accessability to information is
key as you are indicating, not having a comprehensive policy on public
company documents is causing you to have to create this work around.
Just my two cents--- In vantage@yahoogroups .com, "Charlie Wilson"
<foamdesigncsw@ ...> wrote:
>
> All,
>
>
>
> We often use the feature that allows you to "attach" files to
different
> vantage documents such as job methods and orders for purposes of
attaching
> drawings and certification paper work. The only problem with this
feature is
> that the file isn't actually uploaded to the Vantage database instead
I
> record is created with a link to the file where ever it may be. Now I
> understand that this was done to reduce the size of the database but
this
> causes all sorts of problems further down the road.
>
>
>
> One of the problems we are trying to over come is many people for my
company
> have network shares mapped to drive letters on their computer for
example
> share \\fileserv1\ common <file:/// <file:///\\> \\fileserv1\ common>
is mapped to the Z:
> drive. Now when you "attach" a file from this mapped drive vantage
picks up
> the files location as z:\file.txt. the problem this causes is that not
every
> single person has the same drive mappings to when another person
attempts to
> open the file they may get a file not found error because on their
machine
> \\fileserv1\ common <file:/// <file:///\\> \\fileserv1\ common> is
mapped to Y:. So is
> there a way to make vantage detect this absolute mapping so that it
creates
> the record \\fileserv1\ common\file. txt <file:/// <file:///\\>
\\fileserv1\ common\file. txt>
> instead of z:\file.txt.
>
>
>
> I'm also left with the problem of fixing the 2400 files that have
already
> been "attached". To do this I attempted copying all the info out to an
excel
> file and doing a find and replace to fix what I could and then
attempting to
> do a paste update to put all the changes back in from the external
file
> reference app. The problem with this is that when it get to the bottom
of
> the file references that can fit on one screen and it begins to scroll
I get
> a Update could not be completed error message. Any ideas on how to get
past
> this?
>
>
>
> ~Charlie
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
14
That would be too simple, users would never be able to handle that.

User: hey, I don't have the T: drive mapped anymore, I just have K, the Quality drive.
IT: yes, just open K:, look for your Engineering folder
User: well, that's not the right one. I don't know what is in that engineering folder showing in K: but our folder is in T:
IT: no, it's same files as always.
User: but, K: is where Quality puts their documents, we're Engineering, we use T:
IT: <pulls hair out> T: no longer exists, what was in T: is now in K:
User: Why did you move the files in T over to K? K is for Quality, we need to move them back to the T: Drive...
IT: <drinks heavily>

see where this is going? hahaha




________________________________
From: Brian W. Spolarich <bspolarich@...>
To: vantage@yahoogroups.com
Sent: Friday, March 6, 2009 10:40:54 AM
Subject: RE: [Vantage] Re: File Reference Problem


Windows DFS can also help you with this. You can actually just have a
single drive letter, and map all of your shares into a DFS hierarchy
that's the same for everyone in your AD domain.

It works well and can avoid the drive letter madness.

-bws

--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@advanced photonix. com ~ 734-864-5618 ~
www.advancedphotoni x.com

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Tony Hughes
Sent: Friday, March 06, 2009 11:36 AM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Re: File Reference Problem

I agree.
only letter on our network that is different for each user is U: which
maps to their home directory.
T: or K: or whatever needs to be identical for all users, regardless.

____________ _________ _________ __
From: rob.bucek <rob.bucek@yahoo. com <mailto:rob. bucek%40yahoo. com> >
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Sent: Friday, March 6, 2009 9:23:48 AM
Subject: [Vantage] Re: File Reference Problem

Im a root cause guy, i think you need to start by having a central file
server (pick one any one) and make sure that anyone creating electonic
documents that are referenced by others in your company stores them in
your file server. All our drawings, customer specifications, ISO docs,
engineering files (cad) are on one computer/server. Permisions to
individual folders on that drive may vary of course depending on the
nature of what is being stored there. Accessability to information is
key as you are indicating, not having a comprehensive policy on public
company documents is causing you to have to create this work around.
Just my two cents--- In vantage@yahoogroups .com, "Charlie Wilson"
<foamdesigncsw@ ...> wrote:
>
> All,
>
>
>
> We often use the feature that allows you to "attach" files to
different
> vantage documents such as job methods and orders for purposes of
attaching
> drawings and certification paper work. The only problem with this
feature is
> that the file isn't actually uploaded to the Vantage database instead
I
> record is created with a link to the file where ever it may be. Now I
> understand that this was done to reduce the size of the database but
this
> causes all sorts of problems further down the road.
>
>
>
> One of the problems we are trying to over come is many people for my
company
> have network shares mapped to drive letters on their computer for
example
> share \\fileserv1\ common <file:/// <file:///\\> \\fileserv1\ common>
is mapped to the Z:
> drive. Now when you "attach" a file from this mapped drive vantage
picks up
> the files location as z:\file.txt. the problem this causes is that not
every
> single person has the same drive mappings to when another person
attempts to
> open the file they may get a file not found error because on their
machine
> \\fileserv1\ common <file:/// <file:///\\> \\fileserv1\ common> is
mapped to Y:. So is
> there a way to make vantage detect this absolute mapping so that it
creates
> the record \\fileserv1\ common\file. txt <file:/// <file:///\\>
\\fileserv1\ common\file. txt>
> instead of z:\file.txt.
>
>
>
> I'm also left with the problem of fixing the 2400 files that have
already
> been "attached". To do this I attempted copying all the info out to an
excel
> file and doing a find and replace to fix what I could and then
attempting to
> do a paste update to put all the changes back in from the external
file
> reference app. The problem with this is that when it get to the bottom
of
> the file references that can fit on one screen and it begins to scroll
I get
> a Update could not be completed error message. Any ideas on how to get
past
> this?
>
>
>
> ~Charlie
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]