Error 429

[Guest]

Can't create Active-X.

I have a Client that insists I have a single front-end (NOT thin client) w/
its
back-end on a Server...a max of 5 Users take turns on the Front-end.

One of the Users gets Error 429 (the other Users don't), so that means
something is wrong on his PC. Their It Dept has checked the offending PC..at
this point,
they are...

"They are elevating the issue to the next tier for review. If they don't
come up with a solution that "fixes" the issue, they're talking about a
complete re-image of my hard drive."

Any insight on this? TIA - Bob

 

[Douglas J. Steele]

What code is raising the error?

 

[Guest]

Doug - I'm not there...will be tomorrow...but it's automation to
Excel...would be something like (where I am today)...so maybe something on
Excel on the offending PC...

Dim objXLApp As Object 'Excel.Application
Dim objXLWb As Object 'Excel.Workbook
Dim objXLSheet As Object 'Excel.Worksheet
Dim Z As DAO.Database, RS As DAO.Recordset, M$, N$, Q$
Dim AQQ As DAO.QueryDef, PM As DAO.Parameter, A As Byte
Dim RT As DAO.Recordset, D As Double, B As Long
Set Z = CurrentDb
Q = "SELECT [Part Cost] From [Tarts] WHERE PartID = 449;"
Set RT = Z.OpenRecordset(Q, dbOpenSnapshot)
With RT
D = ![Part Cost]: .Close: Set RT = Nothing
End With
Set AQQ = Z.QueryDefs("RepPareto")
For Each PM In AQQ.Parameters
PM.Value = Eval(PM.Name)
Next PM
Set RS = AQQ.OpenRecordset()
With RS
If Not .BOF Then
M = "C:\BobDev\IPRepairCost.xls"
'Open Excel Session
Set objXLApp = CreateObject("Excel.Application")
'open workbook, error routine will create it if doesn't exist
'select desired worksheet
N = "": N = "A" & MonPar & YrPar
Set objXLWb = objXLApp.Workbooks.Open(M)
Set objXLSheet = objXLWb.Worksheets("graph data")
objXLSheet.Range("ThePrice").Clear
objXLSheet.Range("ThePrice") = D
Set objXLSheet = objXLWb.Worksheets("CurMonth")
objXLSheet.Range("First").Clear
...................end of snippet

 

[Douglas J. Steele]

Yeah, sounds like you need to ensure that Excel is installed properly on
that machine.

BTW, looking at the code you posted below, I'd recommend inserting code to
verify that the file actually exists before you open it:

M = "C:\BobDev\IPRepairCost.xls"
'Open Excel Session
If Len(Dir$(M)) > 0 THen
Set objXLApp = CreateObject("Excel.Application")
'open workbook, error routine will create it if doesn't exist
'select desired worksheet
N = "": N = "A" & MonPar & YrPar
Set objXLWb = objXLApp.Workbooks.Open(M)
Set objXLSheet = objXLWb.Worksheets("graph data")
objXLSheet.Range("ThePrice").Clear
objXLSheet.Range("ThePrice") = D
Set objXLSheet = objXLWb.Worksheets("CurMonth")
objXLSheet.Range("First").Clear
Else
MsgBox M & " doesn't exist."
End If



--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Doug - I'm not there...will be tomorrow...but it's automation to
Excel...would be something like (where I am today)...so maybe something on
Excel on the offending PC...

Dim objXLApp As Object 'Excel.Application
Dim objXLWb As Object 'Excel.Workbook
Dim objXLSheet As Object 'Excel.Worksheet
Dim Z As DAO.Database, RS As DAO.Recordset, M$, N$, Q$
Dim AQQ As DAO.QueryDef, PM As DAO.Parameter, A As Byte
Dim RT As DAO.Recordset, D As Double, B As Long
Set Z = CurrentDb
Q = "SELECT [Part Cost] From [Tarts] WHERE PartID = 449;"
Set RT = Z.OpenRecordset(Q, dbOpenSnapshot)
With RT
D = ![Part Cost]: .Close: Set RT = Nothing
End With
Set AQQ = Z.QueryDefs("RepPareto")
For Each PM In AQQ.Parameters
PM.Value = Eval(PM.Name)
Next PM
Set RS = AQQ.OpenRecordset()
With RS
If Not .BOF Then
M = "C:\BobDev\IPRepairCost.xls"
'Open Excel Session
Set objXLApp = CreateObject("Excel.Application")
'open workbook, error routine will create it if doesn't exist
'select desired worksheet
N = "": N = "A" & MonPar & YrPar
Set objXLWb = objXLApp.Workbooks.Open(M)
Set objXLSheet = objXLWb.Worksheets("graph data")
objXLSheet.Range("ThePrice").Clear
objXLSheet.Range("ThePrice") = D
Set objXLSheet = objXLWb.Worksheets("CurMonth")
objXLSheet.Range("First").Clear
...................end of snippet

What code is raising the error?

 

[Guest]

Doug --

Thank you again.

"BTW, looking at the code you posted below, I'd recommend inserting code to
verify that the file actually exists before you open it:" --> Agree..I
usually do that.
I've been blessed to have a lot of access-to-Excel automation, and sometimes
forget to check for the file's existence...will do better.

Bob

Yeah, sounds like you need to ensure that Excel is installed properly on
that machine.

BTW, looking at the code you posted below, I'd recommend inserting code to
verify that the file actually exists before you open it:

M = "C:\BobDev\IPRepairCost.xls"
'Open Excel Session
If Len(Dir$(M)) > 0 THen
Set objXLApp = CreateObject("Excel.Application")
'open workbook, error routine will create it if doesn't exist
'select desired worksheet
N = "": N = "A" & MonPar & YrPar
Set objXLWb = objXLApp.Workbooks.Open(M)
Set objXLSheet = objXLWb.Worksheets("graph data")
objXLSheet.Range("ThePrice").Clear
objXLSheet.Range("ThePrice") = D
Set objXLSheet = objXLWb.Worksheets("CurMonth")
objXLSheet.Range("First").Clear
Else
MsgBox M & " doesn't exist."
End If



--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Doug - I'm not there...will be tomorrow...but it's automation to
Excel...would be something like (where I am today)...so maybe something on
Excel on the offending PC...

Dim objXLApp As Object 'Excel.Application
Dim objXLWb As Object 'Excel.Workbook
Dim objXLSheet As Object 'Excel.Worksheet
Dim Z As DAO.Database, RS As DAO.Recordset, M$, N$, Q$
Dim AQQ As DAO.QueryDef, PM As DAO.Parameter, A As Byte
Dim RT As DAO.Recordset, D As Double, B As Long
Set Z = CurrentDb
Q = "SELECT [Part Cost] From [Tarts] WHERE PartID = 449;"
Set RT = Z.OpenRecordset(Q, dbOpenSnapshot)
With RT
D = ![Part Cost]: .Close: Set RT = Nothing
End With
Set AQQ = Z.QueryDefs("RepPareto")
For Each PM In AQQ.Parameters
PM.Value = Eval(PM.Name)
Next PM
Set RS = AQQ.OpenRecordset()
With RS
If Not .BOF Then
M = "C:\BobDev\IPRepairCost.xls"
'Open Excel Session
Set objXLApp = CreateObject("Excel.Application")
'open workbook, error routine will create it if doesn't exist
'select desired worksheet
N = "": N = "A" & MonPar & YrPar
Set objXLWb = objXLApp.Workbooks.Open(M)
Set objXLSheet = objXLWb.Worksheets("graph data")
objXLSheet.Range("ThePrice").Clear
objXLSheet.Range("ThePrice") = D
Set objXLSheet = objXLWb.Worksheets("CurMonth")
objXLSheet.Range("First").Clear
...................end of snippet

What code is raising the error?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)


Can't create Active-X.

I have a Client that insists I have a single front-end (NOT thin
client)
w/
its
back-end on a Server...a max of 5 Users take turns on the Front-end.

One of the Users gets Error 429 (the other Users don't), so that means
something is wrong on his PC. Their It Dept has checked the offending
PC..at
this point,
they are...

"They are elevating the issue to the next tier for review. If they
don't
come up with a solution that "fixes" the issue, they're talking about a
complete re-image of my hard drive."

Any insight on this? TIA - Bob

 

[Tony Toews [MVP]]

I have a Client that insists I have a single front-end (NOT thin client) w/
its
back-end on a Server...a max of 5 Users take turns on the Front-end.

A single FE? So this resides on the server? And because the 5 users
take turns there are never multiple users in it at the same time?
That's an interesting setup.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Guest]

Tony - True. I explained the correct way to do this (FE on each C: Drive),
but the Customer is the King of this Jungle, so when he growled to FE on the
Server, I explained the negatives of that...he said "That's how we want it".
Been Programming them about 10 years, so I said "Yes Sir !!!". It works
for them.

Bob

 

[David W. Fenton]

I explained the correct way to do this (FE on each C: Drive),
but the Customer is the King of this Jungle, so when he growled to
FE on the Server, I explained the negatives of that...he said
"That's how we want it". Been Programming them about 10 years, so
I said "Yes Sir !!!". It works for them.

A client like this would get a letter stating that any time they
called me in to fix problems caused by this flouting of my stated
strong recommendation would be billed at THREE TIMES my regular
rate.

I actually did this once, and it got the attention of a higher up,
to whom I explained the problem, and then the other person was
ordered to do it my way. Things were rather rough for a while, but
it wasn't all that hot beforehand, either. I ended up entirely
"firing the client" a couple of years later.

 

[Guest]

"I ended up entirely "firing the client" a couple of years later."...
I wouldn't do this to my Clients, unless they got VERY "nasty" w/ me.

This particular Client has treated me quite well...doing little things like
"inviting" to work on days when they have BIG free luncheons, potlucks,
etc. They even let me sleep there when an icestorm forced me to
leave my house for a week in 2003.