UNC, OIPI, and Read-Only (OpenInsight 32-Bit) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"OpenInsight 32-Bit" author:"Ray Chan" author:"Pat McNerthney" author:"Jim Vaughan"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== UNC, OIPI, and Read-Only (OpenInsight 32-Bit) ====
=== At 06 SEP 2002 02:48:22AM Ray Chan wrote: ===
 
 
<QUOTE>
Under 4.1, we still have the problem that if you use UNC notation (\\ServerName\...) vs. mapping (O:\...) the following undesirable events occur:



1) If you print using OIPI, the document is stamped with "This is an Evaluation Copy of the OIPI...."



Use mapping and it goes away. Somewhere in the code OI must still be looking for a "drive letter."



It would be nice to fix this problem as we see benefits in using UNC.



2) If you bring up a databound form or go into table builder, you'll get a message that the dictionary is read-only.



3) Also, any chance of fixing the "changing Default Printer" issue. If this is on the list of things to do, I won't raise this again. I just don't want this to fall thru the crack .



We do want a perfect product right? ;-)) Again, thanks for 4-1



HTH,

Ray Chan
</QUOTE>
----

=== At 06 SEP 2002 02:48PM Pat McNerthney wrote:  ===

<QUOTE>Ray,



  I was unable to reproduce the symptoms you are describing with regards to using UNC.



  How *exactly* are you using UNC'es versus mapped drives?



Pat

</QUOTE>

----

=== At 06 SEP 2002 09:47PM Ray Chan wrote:  ===

<QUOTE>Pat



[i]How *exactly* are you using UNC'es versus mapped drives?[/i]



In the "short-cut" on the desktop, we enter into the "Target" prompt the startup command. If we use a drive letter no problem, e.g., 

 

*** O:\Oinsight\Develop\OINSIGHT.exe *** (Map drive "O" )



However, if we use the UNC notation, then we experience the symptons I described earlier, e.g.,



*** \\ServerName\FolderName\Oinsight\Develop\Oinsight.exe *** (UNC)



Again, the symptons are: 1) when you bring up a databound form in Form Designer, you are told that the dictionary is Read-Only. 2) If you print using OIPI, the "evaulation" message is printed on each page.



Hope this helps. Oh yes we are running Windows 2000 Server with the latest Win 2000 service.



Ray Chan





</QUOTE>

----

=== At 06 SEP 2002 10:57PM Pat McNerthney wrote:  ===

<QUOTE>Ray,



  So far, I am still unable to reproduce the dictionary is read-only symptom.



  What is the "Start in:" directory set to on the short cut?  Also, double and triple check all of the volumes in your database definition to make sure there are not any hard-coded paths in there.  You want all volume paths to be relative the OI directory.



  Does anybody else get Ray's symptoms?



Pat

</QUOTE>

----

=== At 07 SEP 2002 01:33AM Jim Vaughan wrote:  ===

<QUOTE>I just launched

Shortcut: \\jimbo\OI32\OINSIGHT.exe

Start in: \\jimbo\OI32



When I open a form that is bound to data I get a message that says:



The dictionary is read only. 

You will not be able to modify its column attributes. 

</QUOTE>

----

=== At 07 SEP 2002 01:41AM Ray Chan wrote:  ===

<QUOTE>Pat,

[i]What is the "Start in:" directory set to on the short cut? [/i]



If we use UNC, our "Start in" is: [b]\\SName\Folder\Oinsight[/b]



If we use Drive Mapping, out "Start in" is: [b]O:\OINSIGHT[/b]



[i]Also, double and triple check all of the volumes in your database definition to make sure there are not any hard-coded paths in there. You want all volume paths to be relative the OI directory.[/i]



I assume you mean the DBT file. Here we are using the same dbt file as SYSPROG. I looked in an editor just now and there are no fix "drive" letters used within. We attach our file via a routine that is fired when a user logs into OI. We purposely did this so we would not be dependable on a fix "drive letter."



Just in case this makes a difference, here is our folder structure for our application.



Level 1 Folder Application

Level 2 Folder OurData

Level 3 Folder Volume1 of Data

Level 3 Folder volume2 of Data

Level 3 Folder Volume3 of Data



Level 2 Folder Oinsight

Level 3 Folder OI Development (dll & exes)

Level 3 Folder OI Runtime (dll & exes)



Thanks again Pat,

Ray Chan

</QUOTE>

----

=== At 07 SEP 2002 01:44AM Ray Chan wrote:  ===

<QUOTE>Jim,

Ahhh, appreciate you taking the time and helping to validate this problem. Sometimes I start to doubt myself .



Any case, if this is a problem, it should be fixed as we all want the best possible product.



Ray Chan

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=29D0931A0E10130785256C2C00256379|View this thread on the Works forum...]]