Re: MS Access Reports and VB.NET Program

I know vb.net like the back of my hand

ADP isn't a toy.

it's 100 times easier for simple apps; and reporting than all this
'VB.NET Desktop' crap you kids are preaching.

100 times easier to deploy.

It's not 'Access' - as in it's not MDB-- it's real thin Vb6 against SQL
Server.
It kicks ass, for the record.

Rather than paying 3rd-party licensing fees and fighting DLL hell--
don't you wish you could iron out and standardize the UI?

Access ADP is just flat out more powerful than your silly VB.net on the
desktop lol

-Aaron



Izzy wrote:
aaron.kempf@xxxxxxxxx wrote:
.NET for a client app?

I'd have written it in ADP and I'd be done in 1/4 of the time!

It's not always about you Aaron. Maybe you should write that down and
read it once a day, I think it might help.


Who gives a crap about .NET for client development?? I mean; do you
think that I want to ship a 30mb .NET framework to each of my clients?

Well let's see...including myself....millions of developers
worldwide. Except you because you're emotionally attached to one
platform. Someday when you get done playing with your toy (ADP) you can
step into the real development community with the rest of us.

If your clients are running Windows XP then the framework is already
there. Oh but wait...my bad I just realized how emotionally attached
you get to things...your clients pc's are probably still running
Windows 9x.

You know, Barns & Noble has some books that could help you learn .NET.
You're probably thinking all their books are way too advanced for
you, but just start with ".NET For Dummies". You can even read it 2 or
3 times if it helps.



I mean seriously.. Friggin Idiots!

There you go again, a piece of advice Aaron: If you're incapable of
having an intelligent exchange, then it's best to say nothing.
Otherwise you say things like the above and then everyone knows how
ignorant you are.


Keep it in Access Data Projects; no linked tables; nothing complex..
just a single simple ADO connection.

Do some research Aaron, ADO.NET is faster and all around better then
ADO. Your clients will gain performance and your Sql Server will gain
performance. Aaron....step away from the Access books, I know you are
attached to them but you'll like the new .NET books just as much.


It is Access TIMES eCommerce TIMES Sql Server.

Yeah, do your users a favor and go read some books. I love the fact
that you actually posted how to execute the report using a macro. Back
in the day when I did Access development, We use to laugh about
developers who use macros. I'll be sure and forward this to some of my
development buddies so they can get a good laugh. MACRO'S.....LOL

We'll this has been fun Aaron, now reposting here will be a waist of
your time (not as if your not doing that already with ADP). I'm not
reading anymore from you, nor will I be reposting.

Look, all sarcasm aside, read some books and take an objective look at
.NET.

VBA is a toy...always has been....always will be.


-Aaron


Izzy wrote:
aaron.kempf@xxxxxxxxx wrote:
if you upgrade your database to SQL Server you don't have to rewrite
anything; except maybe a couple of sprocs.

Aaron,

Lets say he did upgrade his Access database to Sql Server. Keeping in
mind he's using .NET too write his client app. Are you suggesting using
.NET (which can query Sql Server more efficiently than the Jet engine
using ADO.NET) to send a request to Access which will in turn query Sql
Server sending the results back to Access and be displayed in .NET?

Talk about a performance nightmare.

I'm not saying no one should use Access as thier front end tool. Access
works just fine for some and not for others.

What I'm saying is if you are using Sql Server as your back end and
VB.NET as your front end, then why would you use Access? Unless you
were emotionally attached too it.

Unlock your mind sir.


-Aaron


Izzy wrote:
While opinions will vary as to which is a better reporting tool,
something else to keep in mind is, the future of your database. If this
database will never grow out of Access then I say write the reports in
Access.

If you think this database might someday be upgraded to SQL Server or
Oracle then Crystal will be a much better solution as you wont be
rewriting reports in the future.

Izzy

aaron.kempf@xxxxxxxxx wrote:
or of course you could just shell to the macro

c:\InsertFullPath\MSACCESS.exe "c:\mySilly.mdb" /X macroname

right?

isn't that easier?

Access reports kick Crystal's ass

-aaron


George Shubin wrote:
You need to have the Access application installed (not just the mdb file) on
the computer you want to run the report. Try using this code: (watch out
for word wrap)

Public Sub PrintAccessReport(ByVal sReportName As String, Optional ByVal
sQryName As String = "", Optional ByVal sSQL As String = "")
Dim oAccess As New Access.ApplicationClass
oAccess.Visible = True
oAccess.OpenCurrentDatabase("C:\PathTo\Your\Database.mdb")
oAccess.DoCmd.Minimize()
'Create new query if needed
If sQryName.Length > 0 And sSQL.Length > 0 Then
Try
'oAccess.CurrentDb.QueryDefs.Delete(sQryName)
oAccess.DoCmd.DeleteObject(Access.AcObjectType.acQuery, sQryName)
Catch
'Close and reopen the Access object if above statement failed
oAccess.Visible = False
oAccess.Quit(Access.AcQuitOption.acQuitSaveNone)
System.Runtime.InteropServices.Marshal.ReleaseComObject(oAccess)
oAccess.Visible = True
oAccess.OpenCurrentDatabase("C:\PathTo\Your\Database.mdb")
oAccess.DoCmd.Minimize()
End Try
oAccess.CurrentDb.CreateQueryDef(sQryName, sSQL)
End If
'Preview the report
oAccess.DoCmd.OpenReport(sReportName, Access.AcView.acViewPreview, , ,
Access.AcWindowMode.acDialog)
'Close the Access Instance
If Not oAccess Is Nothing Then
' Call Access Quit method without saving any changes.
oAccess.Quit(Access.AcQuitOption.acQuitSaveNone)
' Use Marshal class' ReleaseComObject to release the Access instance.
System.Runtime.InteropServices.Marshal.ReleaseComObject(oAccess)
' Dereference the oAccess variable.
oAccess = Nothing
End If
End Sub

--
------------------------------------------------------------------------
George Shubin Custom Software Development
dX Software Systems Database Applications
Ph: 503-981-6806 Fax: 503-982-0120
www.dxonline.com george@xxxxxxxxxxxx
------------------------------------------------------------------------

"JoeW" <wajo0401@xxxxxxxxxxxxxxxx> wrote in message
news:1155745516.792909.268870@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm utilizing a database that I created within MS Access within a
program I've created in VB.NET. I am using the VB front end to
navigate the information, but want to be able to print a report, that
I've also created within MS Access. I've attempted using the
Access.Application instance, but I get errors when it tries to load the

database. Just wondering if anyone has any experience with this, and
what I should do.

Thanks for any help you can offer.


.