Hi Nerissa,
lets have a try !

1. When you share data, what is correct, with you old application you do *NOT* have remote data. This is the first mistake you can do. If you choose remote data MM tries to get everything remote (that means over remote views...) and this is not the thing you wan't. It doen't matter where your data is located, if you have VFP Data and Lokal views you have local data.
Perhaps this already helps you out of the problem.
Try to change this behavior back, if you can't do so with MM, do it in registry or ini file (don't know wich one you are using)
In INI File it is:
[Data Settings]
Use Local Data=YES

2. To put up your scenario you need to use more then one Database.
Put up the steps for Additional Databse containers (dev guide) if you habe not already doen.
Then you should have at least two entriees in MetaDBC:
PROJ Projects Database data\proj.dbc
OLDAPP Database of old Application \\myserver\shareddata\oldapp.dbc

This works out realy fine, all with local data!

Marcus


>We currently have one big VFP application that is using a database and free tables placed in one directory. Now our objective is to convert the modules one by one into MM.
>
>When I'm doing my first MM application following the steps in JmpStart document, I found that I will have a problem accessing the tables and databases of our current VFP application. I realized that my MM application will be sharing with our VFP application in the use of these tables. My problem now is how to access those tables. In the first time that I ran my application, I chose "remote data" in the "User Preferences" screen. But I got an error in the second time that I ran the program because it cannot access the default database that MM creates for a project.
>
>So I got a conclusion that my dilemma is how to access those tables and databases that our current VFP application is using.
>
>I will really appreciate any help that you can give to me.
>
>Have a good weekend to everybody.
>
>Nerissa