Replies

More info …

I’ve since found that, on the affected workstations (those with SP1), if I move the file to a local drive, the additional information shows in the InfoTip box. The additional information does not show when the file is on a network drive.

The unaffected machines (those without SP1) do not have this problem — the additional information shows whether the file is on a network drive or on a local drive.

If you wouldn’t mind, could you try moving your file to a network drive to see what happens? Can you see the additional info?

If you wouldn’t mind, could you try moving your file to a network drive to see what happens? Can you see the additional info?

Here’s the exact code I used:

Set dbsNorthwind = CurrentDb
SQL1 = “INSERT INTO tblCylinders(SampleID, CylinderNumber) VALUES([SampleID],’A’);”
dbsNorthwind.Execute SQL1, dbFailOnError

Here’s the exact code I used:

Set dbsNorthwind = CurrentDb
SQL1 = “INSERT INTO tblCylinders(SampleID, CylinderNumber) VALUES([SampleID],’A’);”
dbsNorthwind.Execute SQL1, dbFailOnError

Same thing. I get RTE 3061. “Too few parameters. Expected 1.”

Same thing. I get RTE 3061. “Too few parameters. Expected 1.”

This works (I had to omit the equals sign). I’ll use this method for now, since I’ve not been able to figure out the Execute method.

Thank you.

This works (I had to omit the equals sign). I’ll use this method for now, since I’ve not been able to figure out the Execute method.

Thank you.

>>CurrentDB.Execute SQL1

I can’t seem to get the syntax (or something else) right…

I get Run-time error ‘3601’, Too few parameters. Expected 1.

I found the “Execute Method Example” in help … it’s kind of curious to me. There are two SQL strings in that example … Change … and … Restore.

For the Change string, this is done:

strSQLChange = “UPDATE Employees SET Country = ” & _
“‘United States’ WHERE Country = ‘USA'”
[…]
Set qdfChange = dbsNorthwind.CreateQueryDef(“”, _
strSQLChange)
[…]
ExecuteQueryDef qdfChange, rstEmployees

But for the Restore string, only this is done (which matches the example you gave, i.e., no creating a query def first):

strSQLRestore = “UPDATE Employees SET Country = ” & _
“‘USA’ WHERE Country = ‘United States'”
[…]
dbsNorthwind.Execute strSQLRestore, dbFailOnError

Do I need to create that query def for this to work? But they don’t show a query def for the Restore SQL string, above. Hmmm.

>>CurrentDB.Execute SQL1

I can’t seem to get the syntax (or something else) right…

I get Run-time error ‘3601’, Too few parameters. Expected 1.

I found the “Execute Method Example” in help … it’s kind of curious to me. There are two SQL strings in that example … Change … and … Restore.

For the Change string, this is done:

strSQLChange = “UPDATE Employees SET Country = ” & _
“‘United States’ WHERE Country = ‘USA'”
[…]
Set qdfChange = dbsNorthwind.CreateQueryDef(“”, _
strSQLChange)
[…]
ExecuteQueryDef qdfChange, rstEmployees

But for the Restore string, only this is done (which matches the example you gave, i.e., no creating a query def first):

strSQLRestore = “UPDATE Employees SET Country = ” & _
“‘USA’ WHERE Country = ‘United States'”
[…]
dbsNorthwind.Execute strSQLRestore, dbFailOnError

Do I need to create that query def for this to work? But they don’t show a query def for the Restore SQL string, above. Hmmm.

I’m using Showcase Query to get the data from the AS400 and drop it into Excel. Showcase Query is using ranges actually named “LinkedArea1” … “LinkedArea10”.

It looks like that NameManager might be a useful tool. I’m a little hesitant to try it in this instance though, because I’m afraid it might mess-up the links to Showcase Query (which are tiresome to build, since I’m combining two different datasets on the AS400 into one dataset in Excel).

I’m using Showcase Query to get the data from the AS400 and drop it into Excel. Showcase Query is using ranges actually named “LinkedArea1” … “LinkedArea10”.

It looks like that NameManager might be a useful tool. I’m a little hesitant to try it in this instance though, because I’m afraid it might mess-up the links to Showcase Query (which are tiresome to build, since I’m combining two different datasets on the AS400 into one dataset in Excel).

Yes, exactly. The result is the same as using Union(R1,R2,…). Thank you.

And this is an excellent example of my frustration with the new Help systems in Office/VB. How am I supposed to know that you can do that? That a “range” can take “.cell()” on the end of it to refer to cells within that range? I spent, literally, hours going back and forth and throughout both VB help and Excel help to try to get it to tell me how to do that. It used to be (two versions of Office ago?), knowing little about what I was doing (bet you couldn’t tell :-), I could rely Help, which seemed so much more intuitive then, to help me pound out an application. No longer. For example, if I search for “ranges” the first thing that comes back is something about “SecondValue Property” and a bunch of other (mostly equally useless) stuff (as it relates to what I need to do). Search on “cells” gets me more stuff that gets me close, but never actually gets me there. If I type in “range.cells” or “referring to cells within a range” that gets me there, but who can think to type in exactly that. Very frustrating. I can’t believe I’m the only one experiencing this frustration.

Did they do this just to encourage people to hire programmers??

It doesn’t seem like a course in VB would be the answer, because that’s not going to tell me Range takes .Cell() either. What am I missing?

Yes, exactly. The result is the same as using Union(R1,R2,…). Thank you.

And this is an excellent example of my frustration with the new Help systems in Office/VB. How am I supposed to know that you can do that? That a “range” can take “.cell()” on the end of it to refer to cells within that range? I spent, literally, hours going back and forth and throughout both VB help and Excel help to try to get it to tell me how to do that. It used to be (two versions of Office ago?), knowing little about what I was doing (bet you couldn’t tell :-), I could rely Help, which seemed so much more intuitive then, to help me pound out an application. No longer. For example, if I search for “ranges” the first thing that comes back is something about “SecondValue Property” and a bunch of other (mostly equally useless) stuff (as it relates to what I need to do). Search on “cells” gets me more stuff that gets me close, but never actually gets me there. If I type in “range.cells” or “referring to cells within a range” that gets me there, but who can think to type in exactly that. Very frustrating. I can’t believe I’m the only one experiencing this frustration.

Did they do this just to encourage people to hire programmers??

It doesn’t seem like a course in VB would be the answer, because that’s not going to tell me Range takes .Cell() either. What am I missing?