Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ODBC Driver and Paths
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00453449
Message ID:
00453734
Views:
29
>I have a shared .dbc for a 1-tier VFP app used by dozens of people. I am now tasked with using the Brio report tool to get information out of the .dbc. The .dbc is on server \\gershwin.
>
>Brio uses ODBC to read/present info. Brio is installed on server \\gemini. The %temp% path variable is set to d:\wintemp on \\gemini. I have a System DSN on \\gemini that points to \\gershwin\gendata\gendata.dbc.
>
>When I point Brio to use my ODBC data source, the VFPODBC driver says
SQLGetTypeInfo: rc =-1, SQLSTATE:S1000,Error Msg: [Microsoft][ODBC Visual FoxPro Driver]Cannot open file d:\wintemp\52uk00d.tmp.
>
>When I look at the \\gershwin\gendata directory, I see the .tmp file.
>
>I think the ODBC driver sees the DBC, creates a temp cursor in that location, then tries to convert that to a table and add it to the .dbc, but it forgets to go across the network.
>
>What is the workaround for this?

My guess is that there is no wintemp subfolder beneath the share assigned to D:

If d: is mapped to \\gershwin\gendata, you need a \\gershwin\gendata\wintemp to use your pathing. You also need full privileges in the wintemp folder.

Remember the sharename is mapped to the root of the mapped drive - one reason that mapped drives may be very hazardous. I'd suggest setting the environment variable by UNC if it isn't local.

>
>Help?!
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
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform