Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1579 views

Quotes needed around one filename to open in MSO from Netware serverlocation

In an environment of a few hundred XP Pro systems, using client 4.9SP4,
MS Office 2003 ... Access files are located on a Netware server and MDB
files are correctly associated with Access on the workstation.

For one particular file, double-clicking on a shortcut containing the
filename will not allow it to open; it -appears- as if nothing happens.
In order to open that file, the shortcut has to contain the Access
command line ("...\msaccess.exe") AND the data file name has to be
enclosed in quotes, for the shortcut to work.

For other database files also located on the Netware servers, simply
double-clicking the shortcut to the file suffices to open it in access.

Any ideas why this one file is different, why the quotes around the
filename are needed?

Thanks.

-- DE
Labels (1)
0 Likes
17 Replies
Peter3 Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

Knowing what that specific filename is would be a good start ...


--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

Peter Kuo wrote:
> Knowing what that specific filename is would be a good start ...
>
>

Peter Kuo wrote:
> Knowing what that specific filename is would be a good start ...
>
>

It's a short name, sorry, meant to include that, in the form of
"xxxdata.mdb"

Also I am not sure this is a client-side issue, but since it is not a
long filename, not sure where to start.

Thanks.
0 Likes
Highlighted
ukdtom Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

Try a dir /x for the file, just to make sure......

--
Tommy Mikkelsen
IT Quality A/S, Denmark
Novell Support Forums SYSOP

Sorry, but no support through email
Be a GroupWiseR, go http://www.groupwiser.net

Best Regards Tommy Mikkelsen Denmark Please Report back any success or failure, That way we all learn Sorry, but no support through email "I hate bugs".......Tommy Lee Jones, MIB
0 Likes
Peter3 Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

It may or may not have anything to do with your specific cause, but this
seems interesting:

http://www.eggheadcafe.com/conversation.aspx?messageid=33233460&threadid=33233460

Somtimes when C32 has op. lock enabled, it may cause issues with files
such as Access Database files. You can also try turning op. locks off at
the client:

http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=10085899&sliceId=&docTypeID=DT_TID_1_1&dialogID=61294486&stateId=0%200%2061296313


--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

Peter Kuo wrote:
> It may or may not have anything to do with your specific cause, but this
> seems interesting:
>
> http://www.eggheadcafe.com/conversation.aspx?messageid=33233460&threadid=33233460


Actually, to my understanding, that's why they sit on a Novell server
instead of on a Windows server. I was told it won't work to be shared
if sitting on Windows server. (Well, this file & a host of other shared
databases.)
>
>
> Somtimes when C32 has op. lock enabled, it may cause issues with files
> such as Access Database files. You can also try turning op. locks off at
> the client:
>
> http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=10085899&sliceId=&docTypeID=DT_TID_1_1&dialogID=61294486&stateId=0%200%2061296313


This seems very likely, even though it doesn't superficially look that
way. The symptoms are tickling at something way back in my memory, and
I'm pretty sure that's it. I'm familiar with other issues this raises,
and I know for a fact that it's not disabled at the client.

Thanks; I'll try that.

-- DE

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

If I recall, it's an issue with Database Names with spaces or something
else.
It's been a while since I addressed this issue, but it was an Access issue.

"DE" <nowhere@all.disorg> wrote in message
news:sEkWl.1144$0w7.607@kovat.provo.novell.com...
> In an environment of a few hundred XP Pro systems, using client 4.9SP4, MS
> Office 2003 ... Access files are located on a Netware server and MDB
> files are correctly associated with Access on the workstation.
>
> For one particular file, double-clicking on a shortcut containing the
> filename will not allow it to open; it -appears- as if nothing happens.
> In order to open that file, the shortcut has to contain the Access command
> line ("...\msaccess.exe") AND the data file name has to be enclosed in
> quotes, for the shortcut to work.
>
> For other database files also located on the Netware servers, simply
> double-clicking the shortcut to the file suffices to open it in access.
>
> Any ideas why this one file is different, why the quotes around the
> filename are needed?
>
> Thanks.
>
> -- DE



0 Likes
Peter3 Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

Do let us know what you find!

--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

Thanks, but in this case (not sure how I managed to leave this out of
the first message!) it's an 8.3 name, no spaces or other name oddities.

Also I have not stated the issue well in my subject line, with
apologies. It's really an issue of opening an Access file from the file
or shortcut to it, as opposed to opening it from within Access.

So, for example, if you have documents sitting on a Netware server, and
all the right file associations & extensions, you can open those
documents in Word by double-clicking on the document files or shortcuts
to them.

But in the similar scenario with Access, this one file won't open
through the association, no error, no visible symptoms except nothing
happening.



Craig Wilson wrote:
> If I recall, it's an issue with Database Names with spaces or something
> else.
> It's been a while since I addressed this issue, but it was an Access issue.
>
> "DE" <nowhere@all.disorg> wrote in message
> news:sEkWl.1144$0w7.607@kovat.provo.novell.com...
>> In an environment of a few hundred XP Pro systems, using client 4.9SP4, MS
>> Office 2003 ... Access files are located on a Netware server and MDB
>> files are correctly associated with Access on the workstation.
>>
>> For one particular file, double-clicking on a shortcut containing the
>> filename will not allow it to open; it -appears- as if nothing happens.
>> In order to open that file, the shortcut has to contain the Access command
>> line ("...\msaccess.exe") AND the data file name has to be enclosed in
>> quotes, for the shortcut to work.
>>
>> For other database files also located on the Netware servers, simply
>> double-clicking the shortcut to the file suffices to open it in access.
>>
>> Any ideas why this one file is different, why the quotes around the
>> filename are needed?
>>
>> Thanks.
>>
>> -- DE

>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

Peter Kuo wrote:
> Do let us know what you find!
>

Thanks. No chance to test yet.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

Yeah, I recall the issue.
I just don't recall all the details on what actually caused it.
I think it's a general "Access" issue itself and saw it in the past.

Its a bit hazy, because I have a crazy setup currently for Access DBs.
the Access Extensions are associated to a small Stub application that I
wrote.

The Stub actually opens the start of the DB to see if it is Access 2000,
2003, or 2007 and then opens the DB in that version of Office.
(We have all 3 versions for varying reasons...........sigh............)


"DE" <nowhere@all.disorg> wrote in message
news:DkPXl.2358$0w7.152@kovat.provo.novell.com...
> Thanks, but in this case (not sure how I managed to leave this out of the
> first message!) it's an 8.3 name, no spaces or other name oddities.
>
> Also I have not stated the issue well in my subject line, with apologies.
> It's really an issue of opening an Access file from the file or shortcut
> to it, as opposed to opening it from within Access.
>
> So, for example, if you have documents sitting on a Netware server, and
> all the right file associations & extensions, you can open those documents
> in Word by double-clicking on the document files or shortcuts to them.
>
> But in the similar scenario with Access, this one file won't open through
> the association, no error, no visible symptoms except nothing happening.
>
>
>
> Craig Wilson wrote:
>> If I recall, it's an issue with Database Names with spaces or something
>> else.
>> It's been a while since I addressed this issue, but it was an Access
>> issue.
>>
>> "DE" <nowhere@all.disorg> wrote in message
>> news:sEkWl.1144$0w7.607@kovat.provo.novell.com...
>>> In an environment of a few hundred XP Pro systems, using client 4.9SP4,
>>> MS Office 2003 ... Access files are located on a Netware server and MDB
>>> files are correctly associated with Access on the workstation.
>>>
>>> For one particular file, double-clicking on a shortcut containing the
>>> filename will not allow it to open; it -appears- as if nothing happens.
>>> In order to open that file, the shortcut has to contain the Access
>>> command line ("...\msaccess.exe") AND the data file name has to be
>>> enclosed in quotes, for the shortcut to work.
>>>
>>> For other database files also located on the Netware servers, simply
>>> double-clicking the shortcut to the file suffices to open it in access.
>>>
>>> Any ideas why this one file is different, why the quotes around the
>>> filename are needed?
>>>
>>> Thanks.
>>>
>>> -- DE

>>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

Does "DblClicking" the DB give you the same issue?
If so, you may be able to update the extension association from %1 to "%1"
or something like that.



"Craig Wilson" <craig_d_wilson@yahoo.com> wrote in message
news:59QXl.2389$0w7.1649@kovat.provo.novell.com...
> Yeah, I recall the issue.
> I just don't recall all the details on what actually caused it.
> I think it's a general "Access" issue itself and saw it in the past.
>
> Its a bit hazy, because I have a crazy setup currently for Access DBs.
> the Access Extensions are associated to a small Stub application that I
> wrote.
>
> The Stub actually opens the start of the DB to see if it is Access 2000,
> 2003, or 2007 and then opens the DB in that version of Office.
> (We have all 3 versions for varying reasons...........sigh............)
>
>
> "DE" <nowhere@all.disorg> wrote in message
> news:DkPXl.2358$0w7.152@kovat.provo.novell.com...
>> Thanks, but in this case (not sure how I managed to leave this out of the
>> first message!) it's an 8.3 name, no spaces or other name oddities.
>>
>> Also I have not stated the issue well in my subject line, with apologies.
>> It's really an issue of opening an Access file from the file or shortcut
>> to it, as opposed to opening it from within Access.
>>
>> So, for example, if you have documents sitting on a Netware server, and
>> all the right file associations & extensions, you can open those
>> documents in Word by double-clicking on the document files or shortcuts
>> to them.
>>
>> But in the similar scenario with Access, this one file won't open through
>> the association, no error, no visible symptoms except nothing happening.
>>
>>
>>
>> Craig Wilson wrote:
>>> If I recall, it's an issue with Database Names with spaces or something
>>> else.
>>> It's been a while since I addressed this issue, but it was an Access
>>> issue.
>>>
>>> "DE" <nowhere@all.disorg> wrote in message
>>> news:sEkWl.1144$0w7.607@kovat.provo.novell.com...
>>>> In an environment of a few hundred XP Pro systems, using client 4.9SP4,
>>>> MS Office 2003 ... Access files are located on a Netware server and
>>>> MDB files are correctly associated with Access on the workstation.
>>>>
>>>> For one particular file, double-clicking on a shortcut containing the
>>>> filename will not allow it to open; it -appears- as if nothing
>>>> happens. In order to open that file, the shortcut has to contain the
>>>> Access command line ("...\msaccess.exe") AND the data file name has to
>>>> be enclosed in quotes, for the shortcut to work.
>>>>
>>>> For other database files also located on the Netware servers, simply
>>>> double-clicking the shortcut to the file suffices to open it in access.
>>>>
>>>> Any ideas why this one file is different, why the quotes around the
>>>> filename are needed?
>>>>
>>>> Thanks.
>>>>
>>>> -- DE
>>>

>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

That -is- the issue (though it's .MDB), but, you know, what you wrote
about the %1 looks -so- familiar to me! And it also makes sense,
because to open this file, I have to do a shortcut like

....\msaccess.exe "datafile.mdb"

with the quotes around the name; despite it being a short filename, it
simply won't open without the quotes around the filename.

Like you, I have some vague tickling that I've seen this before & been
able to fix it, but -many- years ago. That could well be it.

Now I won't be able to test until next week, however. Will post back
when I have definite answers!

Thanks.



Craig Wilson wrote:
> Does "DblClicking" the DB give you the same issue?
> If so, you may be able to update the extension association from %1 to "%1"
> or something like that.
>
>
>
> "Craig Wilson" <craig_d_wilson@yahoo.com> wrote in message
> news:59QXl.2389$0w7.1649@kovat.provo.novell.com...
>> Yeah, I recall the issue.
>> I just don't recall all the details on what actually caused it.
>> I think it's a general "Access" issue itself and saw it in the past.
>>
>> Its a bit hazy, because I have a crazy setup currently for Access DBs.
>> the Access Extensions are associated to a small Stub application that I
>> wrote.
>>
>> The Stub actually opens the start of the DB to see if it is Access 2000,
>> 2003, or 2007 and then opens the DB in that version of Office.
>> (We have all 3 versions for varying reasons...........sigh............)
>>
>>
>> "DE" <nowhere@all.disorg> wrote in message
>> news:DkPXl.2358$0w7.152@kovat.provo.novell.com...
>>> Thanks, but in this case (not sure how I managed to leave this out of the
>>> first message!) it's an 8.3 name, no spaces or other name oddities.
>>>
>>> Also I have not stated the issue well in my subject line, with apologies.
>>> It's really an issue of opening an Access file from the file or shortcut
>>> to it, as opposed to opening it from within Access.
>>>
>>> So, for example, if you have documents sitting on a Netware server, and
>>> all the right file associations & extensions, you can open those
>>> documents in Word by double-clicking on the document files or shortcuts
>>> to them.
>>>
>>> But in the similar scenario with Access, this one file won't open through
>>> the association, no error, no visible symptoms except nothing happening.
>>>
>>>
>>>
>>> Craig Wilson wrote:
>>>> If I recall, it's an issue with Database Names with spaces or something
>>>> else.
>>>> It's been a while since I addressed this issue, but it was an Access
>>>> issue.
>>>>
>>>> "DE" <nowhere@all.disorg> wrote in message
>>>> news:sEkWl.1144$0w7.607@kovat.provo.novell.com...
>>>>> In an environment of a few hundred XP Pro systems, using client 4.9SP4,
>>>>> MS Office 2003 ... Access files are located on a Netware server and
>>>>> MDB files are correctly associated with Access on the workstation.
>>>>>
>>>>> For one particular file, double-clicking on a shortcut containing the
>>>>> filename will not allow it to open; it -appears- as if nothing
>>>>> happens. In order to open that file, the shortcut has to contain the
>>>>> Access command line ("...\msaccess.exe") AND the data file name has to
>>>>> be enclosed in quotes, for the shortcut to work.
>>>>>
>>>>> For other database files also located on the Netware servers, simply
>>>>> double-clicking the shortcut to the file suffices to open it in access.
>>>>>
>>>>> Any ideas why this one file is different, why the quotes around the
>>>>> filename are needed?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> -- DE

>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netwareserver location

Peter Kuo wrote:
> Do let us know what you find!
>

Sorry to say, none of this helped so far. I transferred the file to the
local drive, and it opens on double-click properly (in Access.) But
residing on the Novell server, double-clicking *or* just choosing Open
both result in the appearance of nothing happening.

I checked the command associated with the file-type (extension). From
memory (sorry!) it reads like
C:\MSOFFICE\OFFICE11\MSACCESS.EXE /NOSTARTUP "%1"

with quotes as shown (i.e. per discussion here.)

Disabling file caching on the Novell client doesn't help either.

I know there is an answer to this, I saw it years ago but just can't recall!

Did I miss any suggestions, or does anyone else have any other ideas?
I'm now vaguely starting to remember something like this but maybe it
was with WordPerfect, and I think it had to do with the DDE part of the
setups for the action associated with that file extension, but again I
can't remember *what*.

Hmmmm, is it possible the fix was to uncheck "use DDE"? That seems to
be what I remember.

0 Likes
Peter3 Absent Member.
Absent Member.

Re: Quotes needed around one filename to open in MSO from Netware server location

I afraid a more definitive view of what may or may not be happening is to
take a packet trace (say, using WireShark) from the point you double-click
and see what kind of request/response are being sent/received. At least,
that would help to isolate the issue to being on the server side or not
(which likely is the server side since it works when you have the file
local).


--


Peter
eDirectory Rules!
http://www.DreamLAN.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.