Replies

Caz hit it below. Type Alt-F11 to bring up the VBA IDE, then head to Tools -> References, and see if any are flagged as missing. Lemme know how it turns out.

Check the references to see if any are missing in that db.

Or, check out my new favorite hidden function: Partition(). You can use it to group your scores into ranges that you define, then count the number of occurences in those ranges. It’s a great function, check it out in Help.

I got the following response in the MS Newsgroup; It does indeed do the trick — now to dig into the SDK *shudder*

~~~~~~~~~~~~~~~~~~~~
If you open the Quick Links web part (click on the “Content” link, then on the “Quick Links” name) and go to the advanced section, at the bottom of the
page is a textbox called “Store the following data for this Web Part:” with the following items in it:
PORTAL_QUICKLINKS_FOLDER_PATH_HOLDER
“DAV:getlastmodified” DESC
5

The first line tells the web part where to get the information from, the second line is the sort order, and the 3rd line is the number of items to show.

BTW, this is all explained in the help file that comes with the SDK.
~~~~~~~~~~~~~~~~~~~~

I ran into this at the outset as well – it’s a rights and permissions issue. Check this KB article for your exact message and circumstance. Yawp if none of them does the trick for you!

With IIS 5, MDAC 2.5 and Access 2000, I was able to do the following:

Query a db using ADO and display results, with the db open (user = Admin) and with either the table in data sheet view or not open at all.

Post a record using ADO to the same table with the same conditions.

What kind of an error are you getting, what methodology are you using, what’s the landspeed vel…well, you get the idea!

We used Big Blue exclusively for desktop PC’s, notebooks, and servers until 18 months ago. IBM’s desktops have served us well with no more than the normal component failure rate I’ve seen with other major manufacturers. I found IBM’s site to be very forthcoming in terms of BIOS and driver updates, knowledge base searches, etc. Working with a support tech over the phone could be, erm, trying from time to time.

That said, I bought my folks a Dell this past Christmas. They’re all the same components in the case, so it’s really just a matter of whose support and price is better. Good luck with the flat screen!!

Kevin:

Charlotte is right on with the OnNoData event; I trust that all’s working smooth as silk now, eh?

Thanks, Charlotte! That’s why I come here — illumination.

Great! I hope it works out for you.

You’re spot on regarding the record source: when the report opens it checks its record source, notices that it’s a query, executes the query, then displays the data.

As far as the syntax goes – . Maybe a syntactical change between 97 and 2000? At any rate, it appears that the query runs just fine with no brackets, brackets only around the table name, and brackets around both the table name and the field name. Anybody else have any ideas on this one?

In that regard, any thoughts on where one can find a compare/contrast between the the release candidates and the shipping version of XP?

See if this does the trick for you. You might consider a different mechanism for capturing user input, and you’d certainly want more robust error handling , but this should give you a push in the right direction for dynamically generating SQL statements to use as record sources for your reports.

I backsaved to Access 97, but haven’t had a chance to road test it in that version; works in Access 2000, SR2. Both versions are in the zip. HTH!

Lemme see what I an gin up by way of demo, and I’ll post back.

50,000,000 Rory fans can’t be wrong!

Kevin, I know that you’re considering this resolved, but I’m just getting round to checking the threads from the past couple of days. Here’s my : the source for the report is a query, which is just a SQL statement. It sounds like the SELECT and FROM clauses of your SQL statement will always be the same, and the WHERE clause should default to your pre-specified criteria, but if the user wants to have other criteria, the WHERE clause should change accordingly. Sooo, perhaps when the report is launched, you ask the user to specify a date range, or just press . Behind the scenes, you build up your SQL statement in VBA setting the WHERE clause to your default if the user didn’t enter something, or to their date range if they did. Then you can set the record source of the report to that SQL statement.

Sound like something that you’d be interested in?

You like that? Yeah, Jack Palance said I should wear it, that it had “panache”. And really, who’s going to argue with Jack Palance?