By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,961 Members | 2,492 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,961 IT Pros & Developers. It's quick & easy.

2007 Office button Not disabled in runtime?

P: n/a
ARC
Hmmm...This is interesting. While reading info on packaging an Access 2007
runtime app, it's mentioned that a file such as, .accde (mde for 2007) will
be changed to .accdr, where the final r means runtime.

I assume by changing the extension manually yourself from the .accde to
accdr you can then simulate the runtime (instead of the old way of using the
/runtime switch). I tried this, and it works. When you double-click the
..accdr, it launches with no nav. bar, and in what looks to be, run-time
mode.

A previous poster had said the office button is disabled in runtime, which
made me anxious a bit, as I have coded the traditional "File, Open
database", or "File, Backup back-end database", or "File, Register.." to go
under the office button.

To my surprise (very pleasant surprise), with the runtime extension, .accdr,
the nav bar is no longer visible (which is great), however, the office
button is still visible (even better), as is all my custom commands under
the office button. I sure hope this is true in "real" runtime mode, if it
is, I'll be as pleased as punch!

To see what I mean, see: http://www.pcesoft.com/IQruntime.htm

Andy
Sep 8 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Hi, Andy.
I sure hope this is true in "real" runtime mode
Not everything that works in simulated runtime mode works the same in the
real Runtime version. For example, Sharepoint Services doesn't work with
the Access 2007 Runtime version, but it does with the retail version of
Access 2007 in simulated runtime mode. The only way to be sure how your
application acts in real runtime mode is to download the free Access 2007
Runtime version and test it.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
Sep 10 '07 #2

P: n/a
ARC
Thanks, Gunny! Will the runtime install even if you have the full? I have
the full on both my desktop and laptop.

Andy
"'69 Camaro" <Fo**************************@Spameater.orgZERO_SP AMwrote in
message news:e07Fi.437$1n1.212@trnddc02...
Hi, Andy.
>I sure hope this is true in "real" runtime mode

Not everything that works in simulated runtime mode works the same in the
real Runtime version. For example, Sharepoint Services doesn't work with
the Access 2007 Runtime version, but it does with the retail version of
Access 2007 in simulated runtime mode. The only way to be sure how your
application acts in real runtime mode is to download the free Access 2007
Runtime version and test it.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.


Sep 10 '07 #3

P: n/a
Hi,

"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:4i*****************@newssvr23.news.prodigy.ne t...
Thanks, Gunny! Will the runtime install even if you have the full? I have the
full on both my desktop and laptop.
You CAN do that - but better should not.
At launch of the runtime in summer I did that and at first glance there were no
problems. But later I noticed that access crashed more and more when I closed a
database using the ribbon item or by VBA CloseCurrentDatabase. Uninstalling the
runtime didn't help. It took hours to find all the changed files and reg entries
to completely clean up the system. After that the fault was gone.
There also no sense in installing the runtime parallel as you can't really
launch it. It's automatically installed in the same office12 folder as the full
version an just changes some files.

Ciao, Sascha
Sep 10 '07 #4

P: n/a
ARC
Thanks, Sascha!

Did you read the post I had about the re-linking problems dealing with
having the "append only" fields?

Andy
"Sascha Trowitzsch" <ng@moss-soft.dewrote in message
news:fc**********@online.de...
Hi,

"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:4i*****************@newssvr23.news.prodigy.ne t...
>Thanks, Gunny! Will the runtime install even if you have the full? I have
the full on both my desktop and laptop.

You CAN do that - but better should not.
At launch of the runtime in summer I did that and at first glance there
were no problems. But later I noticed that access crashed more and more
when I closed a database using the ribbon item or by VBA
CloseCurrentDatabase. Uninstalling the runtime didn't help. It took hours
to find all the changed files and reg entries to completely clean up the
system. After that the fault was gone.
There also no sense in installing the runtime parallel as you can't really
launch it. It's automatically installed in the same office12 folder as the
full version an just changes some files.

Ciao, Sascha


Sep 10 '07 #5

P: n/a
ARC
Sascha,

One more thing.. You mentioned the "closecurrentdatabase" command, and I had
never really given that much thought.

My exit button in 2007 is calling a proc to backup the backend-db, then
closing all open forms, then finally a docmd.quit. Should I not be using the
quit command?

Ciao, Andy
"Sascha Trowitzsch" <ng@moss-soft.dewrote in message
news:fc**********@online.de...
Hi,

"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:4i*****************@newssvr23.news.prodigy.ne t...
>Thanks, Gunny! Will the runtime install even if you have the full? I have
the full on both my desktop and laptop.

You CAN do that - but better should not.
At launch of the runtime in summer I did that and at first glance there
were no problems. But later I noticed that access crashed more and more
when I closed a database using the ribbon item or by VBA
CloseCurrentDatabase. Uninstalling the runtime didn't help. It took hours
to find all the changed files and reg entries to completely clean up the
system. After that the fault was gone.
There also no sense in installing the runtime parallel as you can't really
launch it. It's automatically installed in the same office12 folder as the
full version an just changes some files.

Ciao, Sascha


Sep 10 '07 #6

P: n/a
Hi Andy,
"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:qd******************@newssvr12.news.prodigy.n et...
Thanks, Sascha!

Did you read the post I had about the re-linking problems dealing with having
the "append only" fields?
I did.
It's just one of many many bugs to be fixed for SP1. AFAIK we still have 5 days
left to report such problem to MS as the current testing of SP1 will end up at
16-09. ;-)

Ciao, Sascha
"Sascha Trowitzsch" <ng@moss-soft.dewrote in message
news:fc**********@online.de...
>Hi,

"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:4i*****************@newssvr23.news.prodigy.n et...
>>Thanks, Gunny! Will the runtime install even if you have the full? I have
the full on both my desktop and laptop.

You CAN do that - but better should not.
At launch of the runtime in summer I did that and at first glance there were
no problems. But later I noticed that access crashed more and more when I
closed a database using the ribbon item or by VBA CloseCurrentDatabase.
Uninstalling the runtime didn't help. It took hours to find all the changed
files and reg entries to completely clean up the system. After that the fault
was gone.
There also no sense in installing the runtime parallel as you can't really
launch it. It's automatically installed in the same office12 folder as the
full version an just changes some files.

Ciao, Sascha



Sep 11 '07 #7

P: n/a
ARC
Oops, I wrote the wrong thing. .. I do close out all open forms first, then
run a backup proc if they haven't already ran one for the day.

Andy
Sep 11 '07 #8

P: n/a
ARC
Hopefully, AFAIK will forward that one to MS. I tried to use MS's contact on
their webpage, but of course, when it went to the sending data phase, it
bombed out. Do'oh!

Take care, Andy
"Sascha Trowitzsch" <ng@moss-soft.dewrote in message
news:fc**********@online.de...
Hi Andy,
"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:qd******************@newssvr12.news.prodigy.n et...
>Thanks, Sascha!

Did you read the post I had about the re-linking problems dealing with
having the "append only" fields?

I did.
It's just one of many many bugs to be fixed for SP1. AFAIK we still have 5
days left to report such problem to MS as the current testing of SP1 will
end up at 16-09. ;-)

Ciao, Sascha
>"Sascha Trowitzsch" <ng@moss-soft.dewrote in message
news:fc**********@online.de...
>>Hi,

"ARC" <an**@andyc.comschrieb im Newsbeitrag
news:4i*****************@newssvr23.news.prodigy. net...
Thanks, Gunny! Will the runtime install even if you have the full? I
have the full on both my desktop and laptop.

You CAN do that - but better should not.
At launch of the runtime in summer I did that and at first glance there
were no problems. But later I noticed that access crashed more and more
when I closed a database using the ribbon item or by VBA
CloseCurrentDatabase. Uninstalling the runtime didn't help. It took
hours to find all the changed files and reg entries to completely clean
up the system. After that the fault was gone.
There also no sense in installing the runtime parallel as you can't
really launch it. It's automatically installed in the same office12
folder as the full version an just changes some files.

Ciao, Sascha




Sep 11 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.