Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 19 NOV 1998 08:33:57AM Gene Sorbo wrote:

Hi again,

I thought of one potential complication to my thought process on attaching AREV files into a new OI application.

Here's what I have thought through for my approach so far:

1) Backup existing AREV files at customer site from Novell server (F:\AREV).)

2) Restore AREV files onto my local hard drive (C:\AREV)

3) Add files to new OpenInsight application - OI will reference the attached files at C:\AREV

4) Develop the OI application on C:\

5) Complete development.

5) Backup completed OI application on C:\, restore to customers server (F:\OI) which will need to reference the AREV files at F:\AREV

Question: Is there a way to 'rename' the path to the attached AREV files in OI after they are attached, or must the tables be dropped from the application, and then reattached at their true location (F:\AREV)? Are there additional complications to this process (i.e., developed panel that is accessing a table on C:\AREV, deploy the panel when table is at F:\AREV)?

Any ideas or better approaches would be appreciated.

Thanks.

Gene ([email protected])


At 19 NOV 1998 09:01AM Don Bakke wrote:

Gene,

If you stay consistent and always keep your data tables in the same directories on the same relative drives (i.e. F:\AREV vs F:\OI and C:\AREV vs C:\OI) then there is something you can do that will help a lot.

When you attach tables in OI and save this database definition, OI stores these tables and their paths in an OS file called appname.DBT. You can open this file up (best if done in AREV) and see these entries. You will notice that these entries store the absolute path of the data tables, however, you can modify these to be relative. Make sure you back this file up first. Once you've done that then simply replace "C:\AREV" with "..\AREV" and your OI application will look for its tables on the same drive it is running on but in the AREV directory.

Depending on how you deploy your application, you may need to manually copy this file onto the server. But this will avoid the need to open your deployed application and re-attach the tables. BTW, everytime you attach a new table and save the database definition your paths will revert to absolute again, so just be on guard for that.

[email protected]

SRP Computer Solutions


At 19 NOV 1998 10:15AM Gene Sorbo wrote:

Don,

Outstanding! My 'attach' table strategy is still a go!

Thanks very much for your quick response. Look forward to helping you in kind some time.

Gene

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/582e834c682e9c93852566c1004a84fe.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1