Do you want create a query-by-form stored proc?
If so, check this [link http://support.microsoft.com/kb/286828/EN-US/]How to implement Query by Form (QBF) in an Access project[/url]
Hope this is what you're looking for.
Yes, that's what the ADP designed for. Just connect to the server/machine where the SQL Server installed. Make sure the client machine can connect to the server.
In the Input Parameters of the report property, type something like this in.
@mymonth=forms!frmreports!txtMonth,@myyear=forms!frmreports!txtYear,@myday=forms!frmreports!txtDay
My variables are @mymonth,@mtyear and @myday, where the frmreports is the form name.
Since DAO is not available in ADP, you have to move to ADP.
If you will move to VC finally, why don't you use MDB as a frontend and use SQL Server as a backend for the time being? Make sure you use a pass thru query to optimize the backend.
You can use Order By with Case.
Something like this
select * from table
where text in ('sunday','evening','morning')
ORDER BY CASE WHEN text = 'sunday' THEN 1
WHEN text = 'evening' THEN 2
WHEN text = 'morning' THEN 3
END
Check NortwindCS.ADP out. Then look at Sale By Year report, it's based on Sale By Year stored procedure and getting DateStart/DateEnd from a Sale By Year dialog form.
The trick is in InputParameters property of the report.
:)
Yes, there is a good exmaple in NorthwindCS.ADP. Check Sale by Year Dialog form out. It's related with Sale By Year report which based on Sale By Year stored procedure.
:)
You can format the result the way you want.
...
print replicate('0', 2-len(convert(varchar(2),month(@EndBillPer))))+ convert(varchar(2),month(@EndBillPer))+'/'+
replicate('0', 2-len(convert(varchar(2),day(@EndBillPer))))+ convert(varchar(2),day(@EndBillPer))+'/'+...
As I replied in my previous post, I agree with SQLBill.
Try this out.
set dateformat mdy
DECLARE @yr char(2),
@mn char(2),
@dy char(2),
@endbillperiodrange varchar(10),
@EndBillPer smalldatetime
set @endbillperiodrange='0404'
set @yr = right(@endbillperiodrange, 2)
set @mn =...
If you are working with Jet Database (MDB), you'd better stick with DAO. Since DAO's still around in Access 2003 and well-designed for MDB files.
If you still want to do this, check this http://www.utteraccess.com/forums/showflat.php?Cat=&Board=access_2000&Number=296677 out.
:)
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.