I don't know if that conveys my meaning, but perhaps someone can point me to a FAQ or some advice on the following:
You are handed a database and told the creator is gone (in this case it is a medical catastrophe reason) for good and you need to manage it.
It has fe/be, but I have only a copy and fe won't open for me because all links are to server locations to which I do not have rights (that doesn't sound right, but it is true).
Opening a form in Design view gives a Design Master/Replication warning message, that I have never seen. I presume that the creator kept a master somewhere, but I may never find that. So I want to work with these replicated (?) pieces of the database, going forward. Do I need to have anything to do with Replication anyway? This is not a high-end application, i.e. no need for great security, or wide distribution. Servers get backed up overnight, so if someone screwed up the previous day's work is available soon, etc.
Bottom line--what are the best practices for picking up a project when you understand most, but not all of it??
Many thanks,
Tom
You are handed a database and told the creator is gone (in this case it is a medical catastrophe reason) for good and you need to manage it.
It has fe/be, but I have only a copy and fe won't open for me because all links are to server locations to which I do not have rights (that doesn't sound right, but it is true).
Opening a form in Design view gives a Design Master/Replication warning message, that I have never seen. I presume that the creator kept a master somewhere, but I may never find that. So I want to work with these replicated (?) pieces of the database, going forward. Do I need to have anything to do with Replication anyway? This is not a high-end application, i.e. no need for great security, or wide distribution. Servers get backed up overnight, so if someone screwed up the previous day's work is available soon, etc.
Bottom line--what are the best practices for picking up a project when you understand most, but not all of it??
Many thanks,
Tom