[AccessD] Access 2010 SP1 issue

David,

  Depending on the severity of the bug and the scope of it, and based on
past experience, a couple of things might happen:

1. They will issue a KB and a hot patch for an immediate fix. 
2. They will issue a KB with a work around and include it in the next SP.
3. They will simply include it in the next SP.
4. They will issue a KB with a work around and not bother to fix it.

  All I can say definitely is that we are still in the very initial stages
with this.  SP1 became available not too long ago and in many places is just
starting to be rolled out.

  If I hear of anything I can pass along, I will.  But in the meantime, it
looks like simply adding EXEC takes care of the problem with the input
parameters.

Jim.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of newsgrps
Sent: Friday, July 22, 2011 05:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access 2010 SP1 issue

Jim,

How do we find out when Microsoft have solved the problem?  Is there 
a website for these things?

Regards

David Emerson
Dalyn Software Ltd
New Zealand

At 23/07/2011, Jim Dettman wrote:

>  BTW, I should have added that your not alone; the bug has already been
>reported to Microsoft.
>
>Jim.
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David McAfee
>Sent: Thursday, July 21, 2011 03:18 PM
>To: Access Developers discussion and problem solving
>Subject: [AccessD] Access 2010 SP1 issue
>
>I have an ADP with a form that gets bound at run-time.
>This has worked flawlessly for several years until this morning.
>
>The user is complaining that the form opens up with all of the fields
>displaying #NAME?
>
>I haven't touched this form, or even the ADP in the longest time so I new
it
>wasn't anything I've done. :)
>
>It works as it is supposed to on my computer and all the other employees in
>his department.
>
>We had him go to another user's computer and  log in as himself. It worked.
>
>So I figured it was tied to his machine. I then realized his is on Win7,
>using Acess2010SP1.
>
>I found out SP1 was just released internally this week. A-HA!
>
>I ended up getting it working by doing this quick fix as shown below:
>I added the "If (SysCmd(acSysCmdAccessVer) = 14) Then" statement.
>
>Private Sub Form_Open(Cancel As Integer)
>    On Error GoTo Form_Open_Error
>Me.RecordSource = ""
>If Nz(Me.OpenArgs, "") <> "" Then ' Is Not Null Then
>     If IsNumeric(Me.OpenArgs) Then
>         Me.InputParameters = "@IncStatJunctID = " & CInt(Me.OpenArgs)
>         If (SysCmd(acSysCmdAccessVer) = 14) Then
>             Me.RecordSource = "EXEC dbo.stpItemDetHist " &
>Me.InputParameters
>         Else
>             Me.RecordSourceQualifier = "dbo"
>             Me.RecordSource = "stpItemDetHist"
>         End If
>
>         'Do a bunch of stuff here
>
>     Else
>         Cancel = True
>     End If
>Else
>     Cancel = True
>End If
>
>
>This works, but technically isn't correct. I need to check for A2010 SP1,
>not just A2010 (Ver14)
>
>Does anyone know how I can check for SP1?
>Exit Sub
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>--
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com