split database or making ACCDE

[hfsitumo2001]

Which one should we make first, split database or making ACCDE. Since I do not know yet in which server we are putting our back end, can I make ACCDE first?

 

[Gasman]

Split, then make accde

 

[theDBguy]

Check out the auto relinker from JStreet.

Developer Downloads - J Street Technology

These free developer downloads are for our fellow developers – we hope you find them useful! If you use a download for commercial purposes all we ask is that you keep the J Street Technology references in the code. Are you stuck on your project? Need help with development? For mentoring and...

www.jstreettech.com

 

[isladogs]

As Gasman said earlier you should split first. In fact, all databases should be split early in the development cycle
Convert the FE to ACCDE just before you deploy the app

 

[The_Doc_Man]

Unless you are prepared to dynamically relink your BE tables, make the split first.

 

[hfsitumo2001]

Unless you are prepared to dynamically relink your BE tables, make the split first.

Thanks a lot to all of you guys

 

[Pat Hartman]

I always include a linked tables form in my apps but it is never available to the general user. It is only available to those people designated as admins and it presents a warning to not to do this unless they needed to move the BE and I'm not there to relink for them.

 

[hfsitumo2001]

I always include a linked tables form in my apps but it is never available to the general user. It is only available to those people designated as admins and it presents a warning to not to do this unless they needed to move the BE and I'm not there to relink for them.

Yes, the same is true for me, I am the Admin as well as the developer of the software. I will put one the button to prompt me where shall I put the back end. Could you give me the sample?

 

[Pat Hartman]

Try this one.

 

[hfsitumo2001]

Try this one.

Thank you Pat, I will look into it. But actually when we split it it already guides us where shall we put right?

 

[gemma-the-husky]

Split the database, because a few things work differently on a split database.

Develop on a .accdb. You can't develop on a .accde. Publish it to end users as an .accde

If you interested, read what Wayne has to say here about reverse engineering a .accde.
It's not a sales pitch, although I do use this tool

Code Protector for Microsoft Access - Protect the VBA source code from being reverse engineered from your MDE and ACCDE files (everythingaccess.com)

 

[Pat Hartman]

when we split it it already guides us where shall we put right?

Yes, but you ALWAYS need a way to relink. Your users don't need it but YOU do. When you are making design changes to the FE, you should copy the BE to your local drive so you can work with test data. You would relink the copy of the FE that you are going to modify to the test BE for testing to prevent accidentally changing production data. When your changes have been validated and it is time to implement them, relink your local, test copy of the FE back to the production BE and then move the new FE to the distribution directory.

When the FE is linked to only one BE, the linked tables manager works fine but if you ever need to link to multiple BE's, the linked tables manager becomes unwieldy. Newer versions of Access have a linked tables manager that is better but it is still confusing.

 

[hfsitumo2001]

Yes, but you ALWAYS need a way to relink. Your users don't need it but YOU do. When you are making design changes to the FE, you should copy the BE to your local drive so you can work with test data. You would relink the copy of the FE that you are going to modify to the test BE for testing to prevent accidentally changing production data. When your changes have been validated and it is time to implement them, relink your local, test copy of the FE back to the production BE and then move the new FE to the distribution directory.

When the FE is linked to only one BE, the linked tables manager works fine but if you ever need to link to multiple BE's, the linked tables manager becomes unwieldy. Newer versions of Access have a linked tables manager that is better but it is still confusing.

Thank you Pat, so can I use your sample?

 

[Pat Hartman]

Sure, that's what it is for. It is not for resale and you are not allowed to post it even on free sites but you can incorporate the forms and code into your own apps.

 

[hfsitumo2001]

Sure, that's what it is for. It is not for resale and you are not allowed to post it even on free sites but you can incorporate the forms and code into your own apps.

Thank you Pat.I will never resale, neither posting in free sites, I just plan to add it on my Admin Form. Thank you again.

 

[Pat Hartman]

You're welcome.