Didn't convert FE to mde is that an issue?

Hi

After splitting my database I didn't covert the FE to a mde. Is that an issue?

If it is, how do I fix it?

I also have to made some changes to the database. If I make changes to the
backend, should I still link the FE that's not a mde or make the current FE
to a MDE and then re-link it.

Thank you in advance.

On Fri, 23 Apr 2010 22:51:01 -0700, forest8
wrote:

Hi

After splitting my database I didn't covert the FE to a mde. Is that an issue?

If it is, how do I fix it?

I also have to made some changes to the database. If I make changes to the
backend, should I still link the FE that's not a mde or make the current FE
to a MDE and then re-link it.

Thank you in advance.


It's not obligatory to make a .mde; in fact you absolutely MUST keep a copy of
the .mdb around, if you are ever to make any design changes to the user
interface in the future. The only advantages of the .mde are that it's a bit
smaller and possibly faster, and that the users won't be able to see your VBA
code or mess around with the design of your forms or reports. You can always
make your .mdb into a .mde at any time.

I would suggest that if you make changes to the structure of tables in the
backend that you open the .mdb frontend; DELETE the links to those table; and
use File... Get External Data... Link to relink to them. The frontend does
cache some information about the tables, and if the cached information doesn't
match the actual table you can get wierd and unpredictable errors. After you
have done so you can proceed to make the .mde file, but again, it's not
required.
--

John W. Vinson [MVP]

Thank you for the response and the reinsurance.

After making the changes, I will ensure that I create a mde.


"John W. Vinson" wrote:

On Fri, 23 Apr 2010 22:51:01 -0700, forest8
wrote:

Hi

After splitting my database I didn't covert the FE to a mde. Is that an issue?

If it is, how do I fix it?

I also have to made some changes to the database. If I make changes to the
backend, should I still link the FE that's not a mde or make the current FE
to a MDE and then re-link it.

Thank you in advance.


It's not obligatory to make a .mde; in fact you absolutely MUST keep a copy of
the .mdb around, if you are ever to make any design changes to the user
interface in the future. The only advantages of the .mde are that it's a bit
smaller and possibly faster, and that the users won't be able to see your VBA
code or mess around with the design of your forms or reports. You can always
make your .mdb into a .mde at any time.

I would suggest that if you make changes to the structure of tables in the
backend that you open the .mdb frontend; DELETE the links to those table; and
use File... Get External Data... Link to relink to them. The frontend does
cache some information about the tables, and if the cached information doesn't
match the actual table you can get wierd and unpredictable errors. After you
have done so you can proceed to make the .mde file, but again, it's not
required.
--

John W. Vinson [MVP]
.