Taking control of db that's split in new enviroment?

[StacyStacy]

Can someone help with this problem?

I created a database for another department that I split and configured the FE to point to the BE via an IP address on my server at my office. It worked perfectly.

The department moved to another location outside of our building. I placed the database on the server in their new location. I configured the FE to point to the BE via a physical driver letter.

'z:\sosvr1\epl database\epl_fe' AND 'z:\sosvr1\epl database\epl_be'.

The problem is that everytime they access the FE it gives them an error message stating that the db cannot find the BE on the drive letter "s". I KNOW ... IT DOES NOT MAKE SENSE.

I tried to correct the problem by configuring the FE to point to the BE via an IP address on their server. It did not work because their administrator could not get the login and password to their server to work.

They also stated that whenever you make modifications in a different enviroment, my office, and bring it to another enviroment, their new building, you will need to take "ownership" of the db in the new environment. Ok ... I did that. I went into the security under the properties of the FE file, and viewed all of the staff that needed full control, and saw that everyone did have full control.

Please help me. I hope I explained this clearly. Even though it does not make sense. I am clueless.

an IP address on my server at my office. It worked perfectly.

 

[ghudson]

Instead of a Drive letter you need to use the UNC to avoid a user not having thier computer mapped to the same drive letter.

\\Server\Partition\Directory\BackEndDatabase.mdb

 

[StacyStacy]

Thanks, but, here's a silly question, isn't that the same thing I was trying to accomplish with configuring the FE to point to the BE via an IP address like the example IP address below?

\\10.10.1.000\sosvr1\epl database\epl_fe AND
\\10.10.1.000\sosvr1\epl database\epl_be


If so, this did not work ... or at least, their IS person could not successfully login into their network. I never encountered that problem when I configured it to an IP address here in our own environment.

 

[ghudson]

Never seen nor heard of doing it with an IP address. If you say it is possible then there is a permissions problem that their network guru's will have to work it out. Good luck!

 

[StacyStacy]

Thanks! I will look into it.