** Oh God Not the DBT file Again !! ** (OpenInsight Specific)
At 02 AUG 1999 01:27:12PM ** Mike Daniel ** wrote:
Yes, it is true the DBT file strikes from out of the abyss.
Added new hd to system it changed my drive letter, tech support said
edit the DBT in arev and change the Drv Ltr. I did now I can see and list all of my tables but only in a RO (ReadOnly) mode.
Any Suggs.?
Thank
Mike Daniel
At 02 AUG 1999 10:21PM Tony Ayling - Harmony Solutions wrote:
Hi Mike
It gives us a lot of grief too. We have got over it by not having tables permanently attached and attaching them at login. This still gave us trouble in later OI releases so we now - at logoff - delete the application DBT and copy sysprog.dbt to the application on again - i.e. it contains only the system data. Works fine for us.
Hope it helps
Regards
Tony Ayling
At 03 AUG 1999 09:02AM ** Mike Daniel ** wrote:
Tony,
Not quite sure what you are talking about I am new to the OI side
Arev I know well. If you can walk me through what you are telling
me once more slowly.
Thanks
Mike
At 06 AUG 1999 12:11AM Tony Ayling - Harmony Solutions wrote:
Hi Mike
We make sure there are no tables permanently attached first.
We have a login window that is the startup window of the application.
The READ event of this window has a script that attaches the volumes required
ATTACH_TABLE("path","account name","")
We also have a staion parameters screen that each user fills in for their PC indicating the path of the data files. We look at this in the script and use it.
I dont know what you use but we have a main MDI window that everything runs from - the CLOSE event includes an OSREAD of SYSPROG.DBT and OSWRITES it to the application name .DBT. So that if any development or updates change the DBT file it is reverted back to the system one again.
If you uneed any more help let me know.
Regards
Tony Ayling