Thanks, but my problem is a little different in that the user is 
allowed to run multiple copies of the app with different databases - 
hence using commandline parameters to pass drive/path info.



To:                     Multiple recipients of list delphi <[EMAIL PROTECTED]>
Send reply to:          [EMAIL PROTECTED]
From:                   "staff@belding" <[EMAIL PROTECTED]>
Subject:                Re: [DUG]:  Paths and UNCs
Date sent:              Fri, 9 Mar 2001 08:47:13 +1300

> Hello Rohit
> 
> I also hit this issue early after switching from Paradox to Interbase.
> Client workstations require connection strings dependent on the connection
> method and neither connection method can use drive letters to connect to the
> IB database.
> 
> Perhaps someone has an elegant solution for this hurdle which appears when
> installing applications on clients.
> 
> What I did was to write an installation assistant program which is
> 1. run in the IB database directory on the IB server, where it creates a
> file containing connection details for clients for each connection method
> (and other details for my use)
> 2. run from a client at installation time, when it retrieves the connection
> information and places it in the clients registry for use by my application.
> 
> This description is brief. I am happy to give you the installation assistant
> if you want it.
> 
> Regards
> 
> Russell
> 
> 
> 
> ----- Original Message -----
> From: Rohit Gupta <[EMAIL PROTECTED]>
> To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> Sent: Thursday, March 08, 2001 11:29 PM
> Subject: [DUG]: Paths and UNCs
> 
> 
> > Working with interbase, because we had lots of non database shared files,
> we
> > use a shared drive instead of the machine name for interbase connect....
> eg
> >
> > m:\vl2\data  where m is say D drive of machine GATE.
> >
> >
> > This allows to use one setting to access interbase and all other files.
> And
> > this works fine with NT workstations.
> >
> > 95/98 workstations though fail.... the error they give make sit obvious
> that
> > they have failed to conver the m:\vl2\data into a valid complete UNC path.
> >
> >
> > Has anyone else had this problem ?  Are there any fixes or solutions ?
> >
> >
> >
> > --------------------------------------------------------------------------
> -
> >     New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> >                   Website: http://www.delphi.org.nz
> > To UnSub, send email to: [EMAIL PROTECTED]
> > with body of "unsubscribe delphi"
> >
> >
> 
> 
> ---------------------------------------------------------------------------
>     New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
>                   Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED] 
> with body of "unsubscribe delphi"
> 


Regards

Rohit

======================================================================
CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New Zealand
PH    (649) 489-2280 
FX    (649) 489-2290
email [EMAIL PROTECTED]  or  [EMAIL PROTECTED]
======================================================================

---------------------------------------------------------------------------
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED] 
with body of "unsubscribe delphi"

Reply via email to