Recent content by srs09

Thank you for fast response! Going to take a look now :)

Is there a similar ColumnHistory functionality for access 2003? I've been looking into this for a while w/o results. Apologies for jumping into this topic but this is exactly what I've been trying to do.

Have successfully created FE/BE. :)

Thanks for info, will watch out for that! :)

I am just finishing up my first real database and getting ready to put it on a shared network drive and be done, then I read this: Front End? Back End?! :eek: Will my database allow multiple user access (2-5 concurrent users) without problems if I were to drop it into a shared network...

Hey there, Since you are doing a monthly report based solely on month, why not simply let the user enter a month and a year, so that the records from those month and year (say, April 2008) would show up without having the user having to enter the first and last date of the month in question...

I poked around a little bit, and the following works! 'On Submit Click 'On Report Open There is a huge difference in terms of speed between this and my previous method. Thank you so much for your help, I have successfully gotten it to work! :)

That's no problem at all, I am already thankful for any help! As for the code, it appears to work, but instead of opening the report, the report seems to get sent to the printer... Any suggestions?

I am sold :)

The solution you have offered here is within the scope of my understanding so I will have no trouble implementing it when I have access to the database late next week. However, is there a way where I can simply pass the strSQL that the user build on the fly via the form interface to the report...

Hi, I think this is what I am looking for! Can you help me get started? In the meanwhile, I am going to look into how to do this...what you say here is familiar but I have not been working with reports through vb. Thanks!

This is my current scenario, where the report's source is the saved query. I am looking to make the report's source the SQL statement itself, that is, a way to pass the SQL statement build on the fly into the report's source at runtime.

Hi, I am new to access 2003 and have been building a database to track internal projects with the help of books and internet resources. My current scenario: I have a report whose source is a query that a user builds on the fly via a form interface that I created. After the user hits submit on...