Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Using Win32Api with VFP
Message
De
14/05/1999 09:46:33
 
 
À
13/05/1999 16:13:45
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Divers
Thread ID:
00218637
Message ID:
00218972
Vues:
33
>Hi there,
>
>Question 1.
>
>I want to use win32api or other tools to list all available server name on the network. Is this possible and how could I accomplish this task in VFP.
>

If you take a look at my NETRESOURCE class (downloadable here on UT as NETRSC.ZIP; you'll also need CLSHEAP.ZIP), there's an example that searches for all shared devices on all servers from all providers (on a big network, this can be slow). Under VFP6, you might want to look at the ANETRESOURCES() function (it's slow on big networks, too.)

>Question 2.
>
>I want to use win32api to select and return path from different drives ( not mapped path ) ( Prefer > \\server1\directory1\dataset3\test.dbf ). What to I need in order to make this work in VFP?
>

Take a look at Bela Bodec's OCX for a better GETDIR() or my example in the FAQ that uses Shell.Application's BrowseForFolder method (requires a relatively current Windows Shell (at least version 4.71), but doesn't require you to distribute an OCX with your application.)

>Question 3.
>
>I know there is a tool in VFP to view the windows registry, is there a function to list all the software in "HKEY_LOCAL_MACHINE\SOFTWARE" registry into an array?
>

There are registry classes available for download here on UT; you might want to look at the FFC Registry class if you're using VFP6.

>Any samples or links for these questions will be greated.
>
>Thanks in advance.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform