If pivot tables and crosstab queries give you what you want and the forms
part doesn't and it doesn't give you a way to remedy it. That is a limiting
factor of the platform\language. Try writing a pivot table or crosstab query
not in a relational database it would take quite a while. However it really
depends on how big a range of columns you need. I did the visible and moved
fields around trick once or twice. The code might be a little lengthy but it
will work well. If that still didn't give you\me enough columns I copied it
added more fields and did the visible trick again. So for instance I needed
between 15 and 30 columns my first form had 15 to 22. Wrote all the code.
Then copied it and used it for a form for columns 23 to 30. This is not
dynamic but it really doesn't matter because the user has no idea nor does
he care. As long as your end user is satisfied and you spent the least
time/money possible implementing your solution I consider that a Success!
"salad" <oi*@vinegar.comwrote in message
news:wG******************@newsread2.news.pas.earth link.net...
Martin wrote:
Total dynamic form creation is not really a good idea in Access. If your
willing to impose some limits to the form or crosstab query you can get
a
pretty convincing result. In the end, it all depends on your exact
needs.
>
Well, a crosstab query gives me the results I want. So does a Pivot
table. The problem with Pivot tables is that the recordsource is
stashed away someplace, not suitable to updating or filtering on the
fly. The problem with a crosstab is that the column count may fluctuate.
Sometimes, your language choice(VB for Access) when you started can be
your
worst mistake.
I disagree. It gives me partially what I want. I think Pivot tables
and crosstabs aren't fully functional. They are cute, but not really
practical...partially implemented.
IMHO, this language is a very high level language that
doesn't give pin point control like for example C++. But for making an
application quickly from scratch its much better than C++.
If you have a large team of programmers and lots of money and time, then
C++ is worthwhile.
HTH
Martin
"salad" <oi*@vinegar.comwrote in message
news:_E*****************@newsread4.news.pas.earthl ink.net...
>Operating in A97.
I didn't receive much of a response conserning Pivot tables in Access.
Pivot tables are nice, but a CrossTab will work for me too.
Using a Pivot table, one is actually launching Excel for data viewing.
I'd prefer the user stay in Access. Creating dynamic crosstab queries
is pretty simple. The problem is that the column count may shrink or
grow depending on the filter.
One can easily open up a crosstab query. Simply use the OpenQuery
command. But this limits the use of dbl-clicks and event procedures.
Can a form be created that can adjust to the column count changes/column
name changes based on a Crosstab?
----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet
News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption
=----
>
----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----