access DAO to ADP

[hair]

Here is the question

I have an access 2002 db and I want to make it an ADP project. I install everything I need, I import the tables and the forms, copy the queries and rebuild the relationships. Is it going to work? If so easy it would be wonderful.

Dan

 

[Kevin_S]

I import the tables and the forms

You don't import tables in an adp file you link the tables in the adp to a large RDBMS (SQL Server). The adp is a project front end to this larger RDBMS and provides enhanced functionality to this large RDBMS by providing interface tools for creating Stored procedures, views, database diagrams, etc...

Also - some things may require a rebuild in the adp but if you keep the names of tables and queries the same this should be limited...

HTH,
Kev

 

[hair]

Hi Kev

Maybe I didn't make myself clear (not maybe, sure)

I don't want to install MS SQL server. The database has 1500 max 2000 new lines in the main table a month.
I can eventualy empty it from time to time, once a year, if I want to, so not the size is the problem.

The thing is I will have two users on it - and I am afraid of conflicts on recordset level, even though the two users will work on different recordsets but on the same table. I tested it already, so a simle .mdb shared in the network and opened in the same time. It works, but considering the loops I am a little afraid of troubles.

I would like to find out if there is a simple way of using the MS SQL engine(provided with MS Office pro) in order to use the tables on the server and the clients connected by odbc, without having to change a lot in the dao code. Mile gave me some tips but yet I am not sure in which way to go. I have never used the sql engine, and maybe I am very wrongwith this one.

Do you think a shared mdb for two users is a bad idea? Has anybody used it like that? That would be the urgent question actualy.

Thanks in advance


Dan

 

[Kevin_S]

ahhh... ok now I see where your going

You dont need to use an adp file - what you need to do is spilt your db into front end / back end in a client server configuration. So what you will end up with is a backend copy of the db (which should contain only the tables) which will sit on the server and then you have a front end to the database (which should have the forms, queries, reports, macros, modules, and LINKS to the tables) on each users desktop. To link the fron end to the back end all you have to do is open the front end copy and then from the file menu choose, File -- Get External Data -- Link Tables. since you be is NOT SQL Server (or another large RDBMS) you don't need to use the ODBC driver - simply navigate to where your back end is located and select the db - then the tables. You will see the links in your front end if you complete this successfully. For more info search on "split database" in this forum.

Now, when you have the front end linked to the back end you can then give the front end to the users who need to have access and you can set your record locking levels under the Tools -- Options -- Advanced tab to control the users ability to edit/open the same record. For more information on this search the forum for "record locking" and record locking levels"...

Do you think a shared mdb for two users is a bad idea? Has anybody used it like that? That would be the urgent question actualy.

A shared mdb (meaning one db that is not split) is not the best idea as you can run into problems with corruption due to users "bumping into" one another in the db - splitting the db is the preferred way to share the data so I would suggest doing it this way (its also not the difficult once you try it but search on spliting th db if you want more info)....

HTH,
Kev

 

[hair]

Thank you Kev, that was what I was looking for
So keeping the same names for the splitted table will make me able to use the code that I have without big chages.

Thanks again

 

[Kevin_S]

So keeping the same names for the splitted table will make me able to use the code that I have without big chages.

Yep. Should be all set...

If you need any other help post back...

HTH & Good Luck,
Kev

 

[hair]

Thank you Kev, have a nice day.

And actually, yes, I'd need some help on a topic posted a while ago, where I still don't find a solution

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=54188

If you got some time or mood or both, you're wellcome
Thanks again

Dan