What other required DLL's ? Is there something required not mentioned in the manual?
Of course. At a minimum you'll need the PostgreSQL DLLs (see below). Future is a beta and as helpful as it would be for Future documentation to describe PostgreSQL installation, admin and interoperability, the first task for the Future manual is to cover Future. Hard enough to keep up with the many rapid, changes these days. :-) I expect that as Future documentation gets more mature and the very intense pace of change slows down a bit, then Future documentation will acquire example sections (as older Manifold versions often have) that show step by step how to install PostgreSQL and other DBMS packages (usually, the free versions of Oracle, SQL Server and DB2) as "hello world" examples of installing those DBMS packages and then connecting to them from Manifold. But until then, for installing and administering PostgreSQL, I recommend the usual FOSS documentation, which is very helpful. Don't take basic installation for granted, by the way, because depending on how you have installed PostgreSQL you could have issues with things like permissions. This, for instance: I expected the references would work, because in my experience, connection strings to a database server are identical no matter from what machine they are run.
...is taking way too much for granted. Yes, sure, connection strings might be similar but your login is different and you could be hitting that server from a different role. For Radian/Future/Viewer integration / interoperability with PostgreSQL I recommend a careful search of this forum. Many people here use PostgreSQL, as it is a fine product and works very well with Radian technology so no doubt many can help you with the details. I only use PostgreSQL installations that somebody else, more knowledgeable than me, has already set up, so I cannot guide you in that as well as others. I would recommend visiting theProduct Downloads page and reading the section on "DLLS for Popular Open Source Packages" and downloading and installing the DLLs as recommended. After MF runs, what other paths matter? I am trying to make a connection to a remote database, not reference a local file...
I gave the example of referencing a local file as a really simple case to emphasize the need to clear your mind of worrying if Future is functioning correctly and instead to focus on the details of the rest of your installation. My best guess is a) missing required *PostgreSQL* dlls, b) incorrect server configuration, c) permissions or network access or roles issues, or something similar. What issues might interfere with MF connecting directly to a remote PostgreSQL database, while allowing MF to connect to the same database server via ODBC?
Same as what I wrote in my prior post, pretty much rephrased as a) through c) above (repeated below). Without looking over your shoulder and knowing every detail it's hard to zero in closer. My advice, however, would be to abstract the question slightly. Ask yourself... Given two completely different machines that are connected by a network, what issues might interfere with an application on one machine connecting to a database on a different machine with a native DBMS connection while connecting just fine through ODBC? Also, look closely at the two different machines. Are there two different versions of PostgreSQL ... either server or client dlls? You could try some variations, like installing and running Future or Future Viewer on the remote machine to see if it can connect to the PostgreSQL database without going through the network. If that works, you can look into your network configuration. 1. Errors involving paths and other system organizational issues, such as not having a file where an absolute path or relative path expects it to be. 2. Failure to configure systems properly, such as having all required dlls on one machine but not on the other machine. 3. Windows administration issues such as permissions and system policies.
|