Dumb ? Client-Engine help

[rcollman]

"Somebody" moved a database that used pervasive from a workstation I will call WSPSQL (which acted like a server) to a Linux server. They also moved an Access database that does a simple file import on user demand.

Why is WSPSQL the only workstation that can import a file into Access database on the Linus server? After two years and a dozen ODBC installs on various systems, I thought I had a couple of simple straight paths. Excell on any workstation can seem to download data (the datafile organization looks different) but error messages about naming conventions pop up in Access when I try to grab any table.

I my current theory is that WSPSQL used to be a server and has the W3"e" dlls and the others don't. "Some-other-contractor-who-shall-remain-nameless" did not clean the machine, Praise the Lord. The other workstations only see one server DSN which I think is an old one I did when I had more hair and is pointed to what looks like the entire database Dictionary file intead of the folder's DDF's that I want. I could go on with more clues and my ignorant tweaks.

Any ideas that might work for a simpleton? I was thinking of installing a Pervasive Engine on another workstation, just for fun. Thanks. Chris

 

[rcollman]

Humm. On my home/office NT network I was able to duplicate the problem. I can import a table into Access but get an error message with a Link file. The application can create a DDF file for each folder (each folder is a company) and this must have some workaround for their field naming convention which uses [ ]. The application also can create a DDF file for all folders.

So I am left with how to create a engine on a Linus server. That other workstations can see. This is not a problem on my NT server, Duh. The soap opera continues. Chris