• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 269
  • Last Modified:

Moving repository directory

I have a number of forms templates in the repository and have them all stores in one directory. I now need to move this directory, where is the repository directory information stored? Currently the durectory is not in my search path but the derived classes can find it no problem. how can I edit the location so all my derived classs are happy?

Thanks, Tom.
0
boardtc
Asked:
boardtc
  • 6
  • 6
1 Solution
 
JimBob091197Commented:
Hi Tom

The Object Repository isn't necessarily one directory.  There is a file in the Delphi Bin directory called DELPHI32.dro which stores information about each object in the repository, including the directory it's found in.

If you change your repository directory, you will need to edit each entry in this file.

Cheers,
JB
0
 
boardtcAuthor Commented:
JimBob,

Perfect, that's what I needed to know. I was thinking last night it must be in the registry..but had no idea about the dro file.

Tom.
0
 
boardtcAuthor Commented:
JimBob,

I edited the dro file. When I try and open the form that inherits from a repository object (first 8 characters are now not clashing) I now get the message: error creating form: ancestor for "the reporistory object I am deriving from" not found. Any ideas what's going on?

On a side note, when I go to File | New one of the pages is my project name and contains my mainform (only unit in project), why is this?

Thanks a lot,

Tom.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
JimBob091197Commented:
Hi Tom

I'll try to work out the 1st problem and get back to you.

Regarding your 2nd point (the side note) Delphi always puts your current open project & all its forms on a page in the File|New page.  This makes it easy to create a second form that is a copy of an existing form.  Not used often I suppose, but useful if you do ever want to do it!!  :)

Bye,
JB
0
 
JimBob091197Commented:
Hi Tom

Had a look at the 1st problem.  Please confirm that this is the order of the steps you took:
1)  Created a project
2)  Moved the repository & edited the dro file.
3)  Open the original project and it gives the error about the ancestor not found.

If these are the steps you took then it's possible that your project source file may need to be edited.  Open your project's dpr file and check that all the entries in the "uses" clause point to valid directories & units.

Let me know what happens.
Cheers,
JB
0
 
boardtcAuthor Commented:
JimBob,

Thanks a lot. Those are indeed the steps, everything is fine in the project source uses (no repository unit mentioned)....

Tom.

0
 
boardtcAuthor Commented:
JimBob,

I found the reason why - the class/form being inherited from must be added to the project, otherwise you get this error. An instance of it is created of course in the project source - what happens with this instance - it's not  used when I create the derived classes right?

Thanks, Tom.
0
 
JimBob091197Commented:
Tom,

It seems you found the reason.
I don't think the base form needs to be created in the project source.  (You can remove Application.CreateForm(...) for the base form.  As long as it's in the uses clause it should work fine.  (Or am I mistaken??)

Cheers,
JB
0
 
boardtcAuthor Commented:
JimBob, yes that worked nicely thanks. On a sidenote, in my ancestor class I have a virtual method that I call in the ancestor but override in each base class. I don't want to implement it in the ancestor but it forces me to have a implementation that just contains ";", and that appears to work fine. Is there a problem doing this - is there a beyyetr way? Thanks, Tom.
0
 
JimBob091197Commented:
If you are ALWAYS going to override the virtual method in an inherited class, then in the base class you can use the "abstract" keyword, like this:

type
  TMyClass = class(TSomething)
    procedure MyVirtualMethod; virtual; abstract;
  end;

By adding "abstract" to the end of the method declaration in the base class (above) you don't need to provide an implementation for the base class.  In the derived classes you add "override" as usual...

Cheers,
Dave
0
 
boardtcAuthor Commented:
Dave/JimBob :-) I appreciate it, great stuff, thanks a million, Tom.
0
 
JimBob091197Commented:
Anytime.  Cheers...

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now