Questions about fpodbc

[Nancy Palmquist]

Rick Hane wrote:

> Last night we installed fpODBC 1.0.13 on our win 2000 pro network.  The 
> install went very well.  The configuration of fp we installed is a 5 
> user development and a 16 user runtime. Now for the questions.
> 
> 1. Printers...  Being on a network we have 9 laser printers, various 
> flavors of HP.  Since when using fpodbs users call a batch file from the 
> server (via a mapped drive) how do I point a given user to a specific 
> network printer?  Yes I can create them in pmaint but what tells fp that 
> user A is to print to printer B.  NOTE: Each user has a specific and 
> unique batch file they call.  Do I use a set pfprinter command in each 
> users batch file?

Printing in filePro is a complex question.  If userA always prints to 
Printer1, then adding the PFPRINTER variable is the way to go.  If UserA 
likes to print to different printers for different things, add -pq to 
the menus and let UserA pick the printer for each print job.

Each user could also have their own CONFIG table set in the batch file. 
  Then any changes they make to Printers in the Printer Maintenance will 
only apply to them.  I use this as a very last resort, since it is more 
difficult to maintain on a network.

Remember that printer destinations on an output format or menu or using 
the PRINTER command will override any setting made with PFPRINTER.

> 
> 2. Since we have a 16 user runtime license why does fp show the "user 
> count" as 5 (the development user license?  Before everyone comes in and 
> starts yelling because they are locked out, will the system recognize 
> the 16 user license even though it displays the 5 user license?
> 
When does it display the 5 user license?  No it will not count users on 
any Native32 version.

> 3. This one I will have to play with but let me ask the question 
> anyway.  I use a lot of menu scripts and batch files to either import 
> from or export to dif files.  On the batch files and in the scripts they 
> list the 'C:' drive because we use to keep the fp directory on each 
> workstation.  To get these to work is it as simple as changing the drive 
> letter to the new mapped drive (ie. V:)?
> 

I highly recommend that if you have to fix this one time you will want 
to make it more flexible for the future:

set PFDATA=v:
set PFDIR=\appl
set PFPROG=v:

Make use of the variables.  I always put these in the batch files - 
never let filePro use that fpsetenv.bat thing.

Then on those commands do the following:

%pfprog%\fp\dreport blah blah

use the v:\appl\fpmerge just like Unix does for IMPORT and EXPORT.

Then if this will always be on the SERVER it would path to:

%PFDATA%%PFDIR%\fpmerge

I only had to rewrite menus once to figure out that using the variables 
was the way to go.  It will also track well when and if you ever move 
stuff to *NIX systems.  They are not exactly the same but switching 
%pfprog% to $PFPROG is as easy as a global search and replace.

Hope that helps.


> Thank you,
> Rick Hane
> Yore Software
> Email: yoresoft at hotmail.com
> Deluxe Stitcher Company Inc.
> Url:www.deluxestitcher.com
> Email: rhane at deluxestitcher.com
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 


-- 
Nancy Palmquist
Virtual Software Systems
PHONE: (412) 835-9417			Web site:  http://www.vss3.com