Transferring MDB to another computer.. Files needed?

[adrift]

I don't wish to create an installation package via developer's edition..

Rather, I just want to copy my MDB to a different computer and allow it to be used. Access 2000 is installed on both computers.

I tried this but first it won't let me edit the database on the other computer because of the different system.wdw files. Also just copying the MDB missed out some directx ocx controls.

The question:

I want the person on the other end to have open ended editing abilities as I do the developer. What files aside from the MDB so i need to copy as well? And what preferences in security etc can I make in MDB file so that anyone can open and edit it?

 

[Lightning]

What files aside from the MDB do i need to copy as well?

For a straight Access application, only the .mdb file.

If you have implemented Access Security, then the relevant .mdw file as well.

If you have included any ActiveX controls, then the relevant control files. You can identify these by checking their entry in the References list ("Tools|References" from any open module). This will give you the full Path and Filename for each control. NOTE: Most ActiveX files require VB to be installed on the PC to work at all.

For more information on using ActiveX controls, see Chapter 16, "Using ActiveX Controls," in Building Applications with Microsoft Access 97, which is available on the "Microsoft Office Professional" Cd.


And what preferences in security etc can I make in MDB file so that anyone can open and edit it?

If you have set up your own security system, then you will need to modify this to give everyone admin rights.

If you have established Access Security using an .mdw file, just ensure that everyone is a member of the Admins group.

If no Access security is set up, everyone should have full access anyway

HTH

Lightning

 

[adrift]

Thank you, very helpful.

can I assume that anyone with access 2000 installed on their computer also has VB installed?

 

[Lightning]

No. By VB I mean the Visual Basic program, NOT VBA, which is installed with Office.

I can't give you any more details on the requirements because, since most of my customers don't have VB installed, I tend not to use ActiveX controls. I just have the general knowledge of them, not the details.

Perhaps someone else who does use them could offer some comments.