I'm re-posting this from the form Forum as mistakenly posted it there
I’d like to export data from a graph to excel where the query is built in the ‘Row Source’ of the graph rather then being defined as a named query (hope this makes sense)
Ordinarily I have been using something like...
Thanks Skip,
That's what I was hoping to avoid as I have some many graphs built this way and want to give the user an option to export data for every one.
I think I was hoping to be able name the query in vba and refer to it that way,Something like
myData = Me.Graph5.Rowsource but I failed...
Hi Skip,
Many thanks for the quick response.
Certainly the row source is a query that was built using the three ... rather then being built in the query section of access and and pointing to it from row source drop-down. It therefore doesn't have a name.
That's what I'm having trouble with...
I’d like to export data from a graph to excel where the query is built in the ‘Row Source’ of the graph rather then being defined as a named query (hope this makes sense)
Ordinarily I have been using something like
DoCmd.OutputTo acQuery, "QueryName", "MicrosoftExcel(*.xls)", "", True, ""...
Thanks PHV
I went back and at looked at MichealRed's module, and your spot-on about changing the format to yyyy,mm,dd
An even better call then I first thought.
Many thanks
Hi Michael Red,
Thanks for your reply. Nice to speak to very man who wrote the whole sherbang in first place.
According to the dates in my holiday table
07/06/2007
20/06/2007
21/06/2007
10/07/2007
11/07/2007
are all holidays
So 7 June 2007 shouldn’t be counted as a...
Hi all,
I’ve been using Michael Red's faq181-261 'Calculate working days between two dates working days' function for a while and it’s proved to be a very useful tool, so can I firstly say thank you to Michael Red for posting his solution.
Using this model I’ve created a sort of makeshift...
Hi all,
I’m going to be distributing a demo version of an app, which I want to allow users to run unrestricted for 6 months, after which time I want to either allow usage with restricted functionality or simply display a messagebox then exit. (Not quite decided on which way to go)
I was...
Thanks for the pointer PHV. Having looked through the help files and doing a ggogle search I'm still a little lost. Well quite a bit lost to be honest.
Could you possibly elaborate for me.
Hi,
I want to reduce the number of queries I have in my database as the whole thing is looking a little bloated. (In excess of 70 queries.) Previously I’ve been using queries to as the source for exporting data to excel which works well e.g.
DoCmd.OutputTo acQuery, "Qry_CaseloadCount"...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.