Split Database issues

[orange]

I wouldn't put the make Table in the front end either. Yes Compact and repair may be the simple answer, but putting the table in another back end or "side end" as HiTechCoach (Boyd) suggested is often done.



I would like to know more about the Make Table requirement.

"Side end" is a name sometimes associated with a separate backend serving as a scratch/work area.

[HiTechCoach]

Wouldn't selecting Compact and Repair on close within the options of the frontend be sufficient? I suppose there is not a guarantee that the user will ever close their application.

I avoid the "Compact and Repair AND Random DESTORY on close". Just to dangerous.

TIP: To help prevnt data loss NEVER run a Compact and Repair without first creating a backup.

[HiTechCoach]

I wouldn't put the make Table in the front end either. Yes Compact and repair may be the simple answer, but putting the table in another back end or "side end" as HiTechCoach (Boyd) suggested is often done.

I would like to know more about the Make Table requirement.

"Side end" is a name sometimes associated with a separate backend serving as a scratch/work area.

I like the "Side end" name.

The only time I use a make table query is for a one time task. I avoid running the same a make table query more than once. I also find it much better to run a delete query to empty the table and then run an append query to add data.

[ItsMe]

...I avoid the "Compact and Repair AND Random DESTORY on close". Just to dangerous....

I agree. But I was referring to the front end file. My question is if you see a disadvantage to compact and repair on the FE file. Considering the FE is only an application, I do not see C&R as a threat. I ask because I use the FE for temp tables, often.

[HiTechCoach]

I agree. But I was referring to the front end file. My question is if you see a disadvantage to compact and repair on the FE file. Considering the FE is only an application, I do not see C&R as a threat. I ask because I use the FE for temp tables, often.

I have seen "Currupt on Close" ... oops .. Compact On Close corrupt an non-compiled (accdb) front end. It caused issues that destroyed some of the data in the back end. I had to recover the data from a backup.

If your front end is a compile database (mde/accde) you are generally OK to run compact on close.. What I find to work better is to have a new front end copied every time the user opens the application so they always have a clean, updated, and compacted application.

[sdel_nevo]

Hi All

many many thanks for the replys they have been great

i took this advice from HiTechCoach

"The only time I use a make table query is for a one time task. I avoid running the same a make table query more than once. I also find it much better to run a delete query to empty the table and then run an append query to add data."
i have changed the query so that i stop creating a temp table, i have now created the tables that used to be tempaoary and run the querys with these, then delete the data held within.

this has mad a massive difference so once again many many thanks

i am now working on refining some other queries, i will add a post to the relivent area

once again i would like to say a big thank you to all who helped me,

Steve

[HiTechCoach]

Steve,

You're welcome. Glad we could assist.