Database is slowing after splitting

[Emmanuel]

So what do you suggest I do please?

What happens if I decide to forget about splitting the database
Then I make sure I disable the shift bypass key
How about that?

[Micron]

So what do you suggest I do please?

Afraid I don't know other than to say research it further as I already suggested because I didn't experience this issue when linking pw protected be tables. Others have asked questions that you didn't answer - you might want to fill in those blanks if you expect them to continue to help. Not splitting it is not a great idea, especially if it is shared. If not and you don't split, make sure you back up the data often; probably at least once per day if it's used daily.

[Minty]

It sounds as if you are trying to protect your data, or your database.

I would have a careful read of this excellent guide from Colin http://www.mendipdatasystems.co.uk/c...ity/4594444323

[Emmanuel]

Try different disks?, not logical partitions, but physical disks if you have more than one.

Yes
Have tried on two different computers and the same problem persists

[Welshgasman]

No not two computers but two different disks.
I was thinking of disk head movement? Even put the be on another computer?

[isladogs]

I suggest you create a persistent connection to your BE. This should cause a noticeable improvement in speed as the FE won't need to keep re-establishing the connection.
To do this you need a small table in the BE -ideally one field and one record to minimise loading time. If necessary, create a dummy table for this purpose.
Now create a form bound to that table and open it HIDDEN when the database starts. Leave the form open, hidden in the background, whilst your FE remains open.

[Emmanuel]

I suggest you create a persistent connection to your BE. This should cause a noticeable improvement in speed as the FE won't need to keep re-establishing the connection.
To do this you need a small table in the BE -ideally one field and one record to minimise loading time. If necessary, create a dummy table for this purpose.
Now create a form bound to that table and open it HIDDEN when the database starts. Leave the form open, hidden in the background, whilst your FE remains open.

Can you give an example for me to see how it will look like
I think that will help me understand what you mean

[isladogs]

Can you give an example for me to see how it will look like
I think that will help me understand what you mean

Yes I can ... though it may not be any simpler than just trying it out for yourself.

Attached is a zip file containing a split DB with FE and BE
The BE contains a single table tblDummy with one field and one record.
The FE has a hidden start form frmStart linked to that BE table and a main form frmMain

To try this out, hold the shift key down whilst you open the FE to bypass the autoexec macro used at startup.
Now go to the linked table manager and relink the BE table to your own BE file path.
Close and re-open the FE.

The BE table will remain linked in the background providing a persistent connection

NOTE:
If, as Minty suggested, you are trying to protect your data or your database, there is another article that may be even more useful on my website:
http://www.mendipdatasystems.co.uk/i...y-2/4594571073

[Emmanuel]

Yes I can ... though it may not be any simpler than just trying it out for yourself.

Attached is a zip file containing a split DB with FE and BE
The BE contains a single table tblDummy with one field and one record.
The FE has a hidden start form frmStart linked to that BE table and a main form frmMain

To try this out, hold the shift key down whilst you open the FE to bypass the autoexec macro used at startup.
Now go to the linked table manager and relink the BE table to your own BE file path.
Close and re-open the FE.

The BE table will remain linked in the background providing a persistent connection

Thanks
Let me check the file out and see what I can make out of it

[Emmanuel]

Yes I can ... though it may not be any simpler than just trying it out for yourself.

Attached is a zip file containing a split DB with FE and BE
The BE contains a single table tblDummy with one field and one record.
The FE has a hidden start form frmStart linked to that BE table and a main form frmMain

To try this out, hold the shift key down whilst you open the FE to bypass the autoexec macro used at startup.
Now go to the linked table manager and relink the BE table to your own BE file path.
Close and re-open the FE.

The BE table will remain linked in the background providing a persistent connection

NOTE:
If, as Minty suggested, you are trying to protect your data or your database, there is another article that may be even more useful on my website:
http://www.mendipdatasystems.co.uk/i...y-2/4594571073

I went through the file and applied it to my database
And am glad to say that it worked
The speed has greatly been improved even after splitting.
Thanks for your time
And thanks the rest of the team
You all are doing a great job

[isladogs]

We were all pleased to help