ODBC Pricing and usage...

[John Esak]

Ahhh! Thaks so much Bob.  Now I can deal with just buying a 5 user license
and I know it will work. Much appreciated.  I was wondering how the .exe
would *know* where the license file was... considering it would be loeaded
in the local memory space on varying machines.

John

> -----Original Message-----
> From: Robert Haussmann [mailto:haussma at nextdimension.net]
> Sent: Friday, February 10, 2006 9:49 PM
> To: john at valar.com; 'Fplist (E-mail)'
> Subject: RE: ODBC Pricing and usage...
>
>
> > Hey, to answer my own question.  Does it mean that to use a multi-user
> > fpODBC license you *MUST* load the executables on one server
> > and all the
> > outlying machines have to load the executables down the
> > network to their own
> > memory space... and everything works that way?  The last time I tried
> > Windows networking, only 10Mb  were available and that was
> > much too slow for
> > this type of operation.  Now, maybe 100Mb would be better?  I
> > have a 1Gb
> > network in my home, so it might work just fine... has anyone
> > tried this?
> > For that matter, does anyone out there run a multi-user fpODBC system?
> >
>
> Hi John--I only have time for a quick response, but here goes:
>
> 1) 100MBit is pretty much required, 1GB preferred
> 2) no problem loading the EXE's from the server
> 3) on the client, use PFLICFILE= to point to the server installation
> and license file.  The license fill will contain the volume
> serial # of the server (shared) drive.  No need to get serial #'s
> from the clients.
> 4) Caveat--this doesn't work under Netware (where drive serial numbers
> are dependent on IP address, network, client version, and other
> factors).
>
> If you have any further questions, just let me know.
>
> Bob Haussmann
> Tabor Children's Services, Inc.