Database in LAN shared folder

Let's see if I can explain this in a different way.  The account you are logged in under when you run the program must not have access to \\PC2\Share.  If it did, then you wouldn't get an error when you run the program and you wouldn't be prompted for a username and password when you type \\192.168.2.10, which I assume is the address for PC2, in the Run command box.  All of the commands you type and any programs you run while you are logged in run with with the same security restrictions that your account has.  So, if you don't have access, then any program you run won't have access either.  The restrictions and limitations of your account are what's known as a security context.  One obvious solution then is to give your account the right to access that location (\\PC2\Share or \\192.168.2.10).  If you're not an administrator, then you may not be able to change the rights your account has.  In that case see an administrator and ask them about increasing the rights for your account.  If this approach isn't doable, then there's a command called RUNAS that allows for running a program under a different account's security rights.  In other words you can be logged into the computer yet launch a program as if it was someone else who is logged in, someone who's account has access to \\PC2\Share.  This is called impersonation.  Using RUNAS you'd have two programs, the one that actually connects to the database, and a very small second program that launches the database program using the RUNAS command.  The database program would then be running as if it were the other account logged in, the one who's username/password you enter when you connect to \\192.168.2.10 from the Run command box.  Here's a link to a page that describes the RUNAS command: http://www.jsiinc.com/subf/tip2500/rh2548.htm

You want a one line answer to this and to the best of my knowledge there isn't one.  Some of the other experts have posted solutions that map a drive letter.  That's the simplest solution available.  The problem with it is that the drive letter is there the whole time the program is running and that means that the user, if it's not you, can do anything they want to the files in the mapped drive while the mapping exists.  I've participated in several questions that asked this same question.  Initially I proposed mapping a drive too, but found that most folks don't want that solution.  They are usually looking for a method that only allows the program to access the shared folder, not the user running the program.

I understand that you're a newbie and I'm trying to make my explanation as simple and straightforward.  I hope this helps.  If you are still confused, then please be specific on where the confusion is and I'll do my best to explain.