Windows 8 Runtime & listboxes not opening records

[Ruegen]

I have a listbox that another subform on the same main pulls results from the column(0) id from (using text box that pulls the list record selected)

When you click once it (listbox) shows the records in the second form for the corresponding. When you double click it opens the record of the selected (listbox)

This works great in Runtime 2010 for all my 32bit staff and vista



however in 64bit win 8 with any runtime including 2013 64bit the database listbox works for a while, then slows and then stops opening the record on double click and when I say slows it slows to a crawl speed like it is looking up the query in the subform instead of just opening the record with the double click.

Any ideas, suggestions? I was thinking mouse double click settings but they seem fine and as I said before it works fine for a while.

I am wondering if it has anything to do with cache, or how access handles cache (like does it require a flush)

[ItsMe]

There is a 2010 64 bit RT. There are also service pack updates

[ItsMe]

You know, I have not done a lot of research on it because I plan on using Office 32 bit. But, why install 2013 64 bit RT?

[Ruegen]

You know, I have not done a lot of research on it because I plan on using Office 32 bit. But, why install 2013 64 bit RT?

...why not?

I installed it after 32 bit didn't work (64bit) then I tried 2013 64bit. Windows 8 is 64bit install.

It's the same problem. The listbox is pulling over 16000 records by the way....

[ItsMe]

Back in the day I made a choice to avoid 64 bit Office if it was at all possible. I don't recall the reasoning but it had to do with functionality. I don't know if this is an option with W8 anymore. I have not dug into it recently. I guess the best question to ask yourself right now is why RT? Regardless of the version, why are you installing RT?

If the answer is because Access is not installed on the machine, then I would do my best to match the RT with the Office version.

If Office version is 2013 64 bit then that would be the RT I would go for. If it is Office 2010 32 bit, I would insta 2010 32bit RT.

Having said that, you might want to make sure that the correct companats are installed on the machine. There may be OS companants missing or Office componants missing that are present in other machines, ie W7 machine with Office 2010. It may not be 32 bit vs 64 bit. You may need a special W8 version Front End App to run on that machine. I don't know for sure.

Edit: or it could be that list boxes are slow compared to queries

[Ruegen]

Back in the day I made a choice to avoid 64 bit Office if it was at all possible. I don't recall the reasoning but it had to do with functionality. I don't know if this is an option with W8 anymore. I have not dug into it recently. I guess the best question to ask yourself right now is why RT? Regardless of the version, why are you installing RT?

If the answer is because Access is not installed on the machine, then I would do my best to match the RT with the Office version.

If Office version is 2013 64 bit then that would be the RT I would go for. If it is Office 2010 32 bit, I would insta 2010 32bit RT.

Having said that, you might want to make sure that the correct companats are installed on the machine. There may be OS companants missing or Office componants missing that are present in other machines, ie W7 machine with Office 2010. It may not be 32 bit vs 64 bit. You may need a special W8 version Front End App to run on that machine. I don't know for sure.

Edit: or it could be that list boxes are slow compared to queries

Yeah there are outlook 2010 64bit and office 2013 64bit as well as the 2013 runtime installed which could cause a conflict. If it weren't for the fact that MYOB requires outlook I wouldn't have installed outlook.

I am also wondering because the form uses a listbox as apposed to a subform it is an onclick event rather than oncurrent event.

Wondering if I can have an oncurrent for a listbox...