Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Slow detection of absent UNC
Message
De
17/11/2007 09:21:58
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
17/11/2007 09:09:24
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Versions des environnements
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01269426
Message ID:
01269657
Vues:
15
>>>>>>>When a built-in function like DIRECTORY(), FILE() or FCREATE() is passed a UNC-path that does not (no longer) exist, it takes a very long time to tell you that. Is there an API function that can tell this much quicker?
>>>>>>
>>>>>>What is "a very long time"?
>>>>>
>>>>>A minute.
>>>>
>>>>Check your DNS setup. I can see both existent and none existent shares in under 2 seconds across a WAN.
>>>
>>>NSLOOKUP gives quick response.
>>>
>>>Suppose the whole not-existing UNC is '\\K1126SF\APPS\TESTDATA\504\SPL\LIVE' and I do in a Dos box:
>>>
nslookup k1126sf
the result is immediate.
>>>
>>>Might this also be a promissing workaround?
>>
>>Out of interest (to find out if it's a DNS or WINS issue) can you try with an IP address rather than a UNC, e.g.:
>>
>>USE \\192.168.0.5\DataFolder\MyTable ...
>>
>
>I'll try this monday. I'm currently not on that network.

Nevermind I tried that N times before and now, doesn't help. It only helps if it exists.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform