Access 2007

[Lou O]

I have been using Access 2007 for a number of months and have
successfully deployed ACCDR files on many client machines.
The client machines have the "free" Access runtime version installed.
I recently installed SP1 for Office 2007 on my computer.
Now when I make an ACCDE file to distribute, I get an error on client
machines something like
"database is in an unrecognized format".
There seems to be a compatibility problem between Office 2007 SP1 and
Access07 runtime.
I uninstalled Office 2007 completely on my machine, reinstalled
without SP1 and the problem went away.
However MS promptly sent me automatic updates with SP1 included so it
seems they think it's OK to install. I reinstalled SP1 and the problem
is back.
Does anyone know of this issue and what the solution is or if there is
one?
Is there perhaps a new runtime version available that overcomes this
problem? I looked but haven't found it.
Please somebody help!

[Salad]

Re: Access 2007

Lou O wrote:

I have been using Access 2007 for a number of months and have
successfully deployed ACCDR files on many client machines.
The client machines have the "free" Access runtime version installed.
I recently installed SP1 for Office 2007 on my computer.
Now when I make an ACCDE file to distribute, I get an error on client
machines something like
"database is in an unrecognized format".
There seems to be a compatibility problem between Office 2007 SP1 and
Access07 runtime.
I uninstalled Office 2007 completely on my machine, reinstalled
without SP1 and the problem went away.
However MS promptly sent me automatic updates with SP1 included so it
seems they think it's OK to install. I reinstalled SP1 and the problem
is back.
Does anyone know of this issue and what the solution is or if there is
one?
Is there perhaps a new runtime version available that overcomes this
problem? I looked but haven't found it.
Please somebody help!
>

Wouldn't your clients need to update their Service packs as well?

I have A2003 SP2 on my machine. My clients had SP1 for their runtime on
their machines. I had them DL the SP2 file (quite large I must say) and
install it on their individual machines. We're now all up to date. I
suppose the same would be for A2007 as well.

Lonely Girl

http://www.youtube.com/watch?v=rDLmXdHepFw

[Lou O]

Re: Access 2007

Your suggestion was my first "solution". I should have mentioned it in
my first post.
However when I tried to install SP1 on the machines with Access
runtime installed, I received the message that "there is nothing to
update on this computer".
That's when I posted my problem.
Any other ideas?

Salad wrote:

Lou O wrote:

I have been using Access 2007 for a number of months and have
successfully deployed ACCDR files on many client machines.
The client machines have the "free" Access runtime version installed.
I recently installed SP1 for Office 2007 on my computer.
Now when I make an ACCDE file to distribute, I get an error on client
machines something like
"database is in an unrecognized format".
There seems to be a compatibility problem between Office 2007 SP1 and
Access07 runtime.
I uninstalled Office 2007 completely on my machine, reinstalled
without SP1 and the problem went away.
However MS promptly sent me automatic updates with SP1 included so it
seems they think it's OK to install. I reinstalled SP1 and the problem
is back.
Does anyone know of this issue and what the solution is or if there is
one?
Is there perhaps a new runtime version available that overcomes this
problem? I looked but haven't found it.
Please somebody help!

Wouldn't your clients need to update their Service packs as well?
>
I have A2003 SP2 on my machine. My clients had SP1 for their runtime on
their machines. I had them DL the SP2 file (quite large I must say) and
install it on their individual machines. We're now all up to date. I
suppose the same would be for A2007 as well.
>
Lonely Girl
http://www.youtube.com/watch?v=rDLmXdHepFw

[Rick Brandt]

Re: Access 2007

Salad wrote:

That's beyond bizarre! I went to MS and the Access Runtime page was
dated 7/20/07.

MS dropping the ball on something is bizarre? This has been discussed a lot and
yes the current situation breaks the runtime for a lot of developers who aren't
aware of the issue. If there is a work-around (other than the developer
uninstalling SP1) I haven't heard of it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Salad]

Re: Access 2007

Rick Brandt wrote:

Salad wrote:
>

>>That's beyond bizarre! I went to MS and the Access Runtime page was
>>dated 7/20/07.

>
>
MS dropping the ball on something is bizarre? This has been discussed a lot and
yes the current situation breaks the runtime for a lot of developers who aren't
aware of the issue. If there is a work-around (other than the developer
uninstalling SP1) I haven't heard of it.
>

Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
plugged in the wrong search words. BTW, I used to search for *Access*
in groups in GroupsGoogle but any and all groups come up from searces
....even Google is broken.

I mentioned in the past, as a joke, SP3 for A2003 was one way to force
folds to A2007. Now that folks are on A2007 runtime (they have the rest
of Office 2007) the tease is to get them to full version now with a
broken version.

I wonder if anybody is aware of this at MS. It's quite possible people
that can make decisions about it are clueless.

[Lou O]

Re: Access 2007

On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:

Rick Brandt wrote:

Salad wrote:

>

>That's beyond bizarre! I went to MS and the Access Runtime page was
>dated 7/20/07.

>

MS dropping the ball on something is bizarre? This has been discussed a lot and
yes the current situation breaks the runtime for a lot of developers who aren't
aware of the issue. If there is a work-around (other than the developer
uninstalling SP1) I haven't heard of it.

>
Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
plugged in the wrong search words. BTW, I used to search for *Access*
in groups in GroupsGoogle but any and all groups come up from searces
...even Google is broken.
>
I mentioned in the past, as a joke, SP3 for A2003 was one way to force
folds to A2007. Now that folks are on A2007 runtime (they have the rest
of Office 2007) the tease is to get them to full version now with a
broken version.
>
I wonder if anybody is aware of this at MS. It's quite possible people
that can make decisions about it are clueless.

I have sent my original post off to MS and they replied that they will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the 3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the difference.
Stay tuned.

[Salad]

Re: Access 2007

Lou O wrote:

On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:
>

>>Rick Brandt wrote:
>>

>>>Salad wrote:

>>

>>>>That's beyond bizarre! I went to MS and the Access Runtime page was
>>>>dated 7/20/07.

>>

>>>MS dropping the ball on something is bizarre? This has been discussed a lot and
>>>yes the current situation breaks the runtime for a lot of developers who aren't
>>>aware of the issue. If there is a work-around (other than the developer
>>>uninstalli ng SP1) I haven't heard of it.

>>
>>Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
>>plugged in the wrong search words. BTW, I used to search for *Access*
>>in groups in GroupsGoogle but any and all groups come up from searces
>>...even Google is broken.
>>
>>I mentioned in the past, as a joke, SP3 for A2003 was one way to force
>>folds to A2007. Now that folks are on A2007 runtime (they have the rest
>>of Office 2007) the tease is to get them to full version now with a
>>broken version.
>>
>>I wonder if anybody is aware of this at MS. It's quite possible people
>>that can make decisions about it are clueless.

>
>
I have sent my original post off to MS and they replied that they will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the 3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the difference.
Stay tuned.

Should be interesting. One thing. Can you tell me if your other users
of this app have other Office components like Word or Excel? If you
went to About on those programs does it say SP1? This is just for
curiousity's sake.

[Lou O]

Re: Access 2007

On Feb 23, 4:46 pm, Salad <o...@vinegar.c omwrote:

Lou O wrote:

On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:

>

>Rick Brandt wrote:

>

>>Salad wrote:

>

>>>That's beyond bizarre! I went to MS and the Access Runtime page was
>>>dated 7/20/07.

>

>>MS dropping the ball on something is bizarre? This has been discussed a lot and
>>yes the current situation breaks the runtime for a lot of developers who aren't
>>aware of the issue. If there is a work-around (other than the developer
>>uninstallin g SP1) I haven't heard of it.

>

>Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
>plugged in the wrong search words. BTW, I used to search for *Access*
>in groups in GroupsGoogle but any and all groups come up from searces
>...even Google is broken.

>

>I mentioned in the past, as a joke, SP3 for A2003 was one way to force
>folds to A2007. Now that folks are on A2007 runtime (they have the rest
>of Office 2007) the tease is to get them to full version now with a
>broken version.

>

>I wonder if anybody is aware of this at MS. It's quite possible people
>that can make decisions about it are clueless.

>

I have sent my original post off to MS and they replied that they will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the 3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the difference.
Stay tuned.

>
Should be interesting. One thing. Can you tell me if your other users
of this app have other Office components like Word or Excel? If you
went to About on those programs does it say SP1? This is just for
curiousity's sake.

I don't think any of my users have Office 2007 on their machines but
I'll ask anyway.

[ARC]

Re: Access 2007

I've heard estimates of 1st qtr 2008 for the next runtime release. I've been
told they're working on it, so hopefully it won't be much longer. I've been
waiting for the long awaited runtime fixes for the "OutputTo" commands,
which I hope are on the way. And fixes for right-click / short-cut menu
issues. All in all, however, the access 2007 runtime has been very stable
for my runtime users.

Andy
"Lou O" <lgeastwood@gma il.comwrote in message
news:afa25200-6869-44cb-864e-4af33dd29b6d@c3 3g2000hsd.googl egroups.com...

On Feb 23, 4:46 pm, Salad <o...@vinegar.c omwrote:

>Lou O wrote:

On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:

>>

>>Rick Brandt wrote:

>>

>>>Salad wrote:

>>

>>>>That's beyond bizarre! I went to MS and the Access Runtime page was
>>>>dated 7/20/07.

>>

>>>MS dropping the ball on something is bizarre? This has been discussed
>>>a lot and
>>>yes the current situation breaks the runtime for a lot of developers
>>>who aren't
>>>aware of the issue. If there is a work-around (other than the
>>>developer
>>>uninstalli ng SP1) I haven't heard of it.

>>

>>Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
>>plugged in the wrong search words. BTW, I used to search for *Access*
>>in groups in GroupsGoogle but any and all groups come up from searces
>>...even Google is broken.

>>

>>I mentioned in the past, as a joke, SP3 for A2003 was one way to force
>>folds to A2007. Now that folks are on A2007 runtime (they have the
>>rest
>>of Office 2007) the tease is to get them to full version now with a
>>broken version.

>>

>>I wonder if anybody is aware of this at MS. It's quite possible people
>>that can make decisions about it are clueless.

>>

I have sent my original post off to MS and they replied that they will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the 3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the difference.
Stay tuned.

>>
>Should be interesting. One thing. Can you tell me if your other users
>of this app have other Office components like Word or Excel? If you
>went to About on those programs does it say SP1? This is just for
>curiousity's sake.

>
I don't think any of my users have Office 2007 on their machines but
I'll ask anyway.

[Lou O]

Re: Access 2007

On Feb 24, 1:37 am, "ARC" <PCES...@PCESof t.invalidwrote:

I've heard estimates of 1st qtr 2008 for the next runtime release. I've been
told they're working on it, so hopefully it won't be much longer. I've been
waiting for the long awaited runtime fixes for the "OutputTo" commands,
which I hope are on the way. And fixes for right-click / short-cut menu
issues. All in all, however, the access 2007 runtime has been very stable
for my runtime users.
>
Andy"Lou O" <lgeastw...@gma il.comwrote in message
>
news:afa25200-6869-44cb-864e-4af33dd29b6d@c3 3g2000hsd.googl egroups.com...
>

On Feb 23, 4:46 pm, Salad <o...@vinegar.c omwrote:

Lou O wrote:
On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:

>

>Rick Brandt wrote:

>

>>Salad wrote:

>

>>>That's beyond bizarre! I went to MS and the Access Runtime page was
>>>dated 7/20/07.

>

>>MS dropping the ball on something is bizarre? This has been discussed
>>a lot and
>>yes the current situation breaks the runtime for a lot of developers
>>who aren't
>>aware of the issue. If there is a work-around (other than the
>>developer
>>uninstallin g SP1) I haven't heard of it.

>

>Thanks Rick. I went to GoogleGroups and didn't find much...I suppose I
>plugged in the wrong search words. BTW, I used to search for *Access*
>in groups in GroupsGoogle but any and all groups come up from searces
>...even Google is broken.

>

>I mentioned in the past, as a joke, SP3 for A2003 was one way to force
>folds to A2007. Now that folks are on A2007 runtime (they have the
>rest
>of Office 2007) the tease is to get them to full version now with a
>broken version.

>

>I wonder if anybody is aware of this at MS. It's quite possible people
>that can make decisions about it are clueless.

>

I have sent my original post off to MS and they replied that they will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the 3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the difference.
Stay tuned.

>

Should be interesting. One thing. Can you tell me if your other users
of this app have other Office components like Word or Excel? If you
went to About on those programs does it say SP1? This is just for
curiousity's sake.

>

I don't think any of my users have Office 2007 on their machines but
I'll ask anyway.

OK, here's the latest from MS support.
They referred me to the following article;

http://support.microsoft.com/kb/946205/en-us

The gist of it is that you need to update the MSACCESS.EXE file on the
client runtime machine with your current MSACCESS.EXE file that has
the SP1 update on it.
In other words you need to package the MSACCESS.EXE file with your
install package.
But here's the kicker. You need to uninstall the SP1 exe file after
opening the db file in runtime! And they expect my users to put up
with that kind of nonsense!!?
I wish I could go back to A97...nah, it had tons of bugs too.
I'll just run with 07 without the SP1 update and see what comes down
the pipe as time goes by.
Nice one MS!

[ARC]

Re: Access 2007

I, unlike many, have found a2007 to be more stable than a97, but then again,
I had an xp machine with good old blue screens (it was less with a2007 for
whatever reason).

I think the best approach is to NOT load SP1 on your dev pc until the SP1 is
also available for the Runtime. Once it is, update to sp1, compile a new
version, and create an install that is using the sp1 runtime.

Take care,

Andy
"Lou O" <lgeastwood@gma il.comwrote in message
news:414288ed-770a-4290-8349-fa17cd5e1438@j2 8g2000hsj.googl egroups.com...

On Feb 24, 1:37 am, "ARC" <PCES...@PCESof t.invalidwrote:

>I've heard estimates of 1st qtr 2008 for the next runtime release. I've
>been
>told they're working on it, so hopefully it won't be much longer. I've
>been
>waiting for the long awaited runtime fixes for the "OutputTo" commands,
>which I hope are on the way. And fixes for right-click / short-cut menu
>issues. All in all, however, the access 2007 runtime has been very stable
>for my runtime users.
>>
>Andy"Lou O" <lgeastw...@gma il.comwrote in message
>>
>news:afa2520 0-6869-44cb-864e-4af33dd29b6d@c3 3g2000hsd.googl egroups.com...
>>

On Feb 23, 4:46 pm, Salad <o...@vinegar.c omwrote:
>Lou O wrote:
On Feb 23, 2:23 pm, Salad <o...@vinegar.c omwrote:

>>

>>Rick Brandt wrote:

>>

>>>Salad wrote:

>>

>>>>That's beyond bizarre! I went to MS and the Access Runtime page
>>>>was
>>>>dated 7/20/07.

>>

>>>MS dropping the ball on something is bizarre? This has been
>>>discussed
>>>a lot and
>>>yes the current situation breaks the runtime for a lot of
>>>developers
>>>who aren't
>>>aware of the issue. If there is a work-around (other than the
>>>developer
>>>uninstalli ng SP1) I haven't heard of it.

>>

>>Thanks Rick. I went to GoogleGroups and didn't find much...I
>>suppose I
>>plugged in the wrong search words. BTW, I used to search for
>>*Access*
>>in groups in GroupsGoogle but any and all groups come up from
>>searces
>>...even Google is broken.

>>

>>I mentioned in the past, as a joke, SP3 for A2003 was one way to
>>force
>>folds to A2007. Now that folks are on A2007 runtime (they have the
>>rest
>>of Office 2007) the tease is to get them to full version now with a
>>broken version.

>>

>>I wonder if anybody is aware of this at MS. It's quite possible
>>people
>>that can make decisions about it are clueless.

>>

I have sent my original post off to MS and they replied that they
will
work with me to resolve the "incident" (as they have call it).
So someone at MS is aware of this now, although I suspect it's
someone
outsourced somewhere offshore; likely not a decision maker.
Maybe with the runtime being offered free, MS isn't as motivated to
update it as regularly as the retail version. If the tease theory is
true, that would really be low.
I suspect though that MS will get around to updating the runtime
sooner or later.
In any event I unistalled and reinstalled Office07 again (for the
3rd
time!) without SP1 and my app works fine on runtime again. One
important step though was I had to decompile and recompile the
database before it would work.
This makes me think, as a possible workaround I may try (if I think
I
can stomach any more of this) installing SP1 again then decompiling
and recompiling the database to see if that might make the
difference.
Stay tuned.

>>

>Should be interesting. One thing. Can you tell me if your other
>users
>of this app have other Office components like Word or Excel? If you
>went to About on those programs does it say SP1? This is just for
>curiousity's sake.

>>

I don't think any of my users have Office 2007 on their machines but
I'll ask anyway.

>
OK, here's the latest from MS support.
They referred me to the following article;

http://support.microsoft.com/kb/946205/en-us

The gist of it is that you need to update the MSACCESS.EXE file on the
client runtime machine with your current MSACCESS.EXE file that has
the SP1 update on it.
In other words you need to package the MSACCESS.EXE file with your
install package.
But here's the kicker. You need to uninstall the SP1 exe file after
opening the db file in runtime! And they expect my users to put up
with that kind of nonsense!!?
I wish I could go back to A97...nah, it had tons of bugs too.
I'll just run with 07 without the SP1 update and see what comes down
the pipe as time goes by.
Nice one MS!