How to grasp the DB concepts in VB.Net (VSTO)?
How to grasp the DB concepts in VB.Net (VSTO)?
Hi Guys,
I bring to you my extensive background with VBA and Ms Access databases. Recently, I've started using VSTO Word Document features to build detailed reports, as the Reporting Tools in Ms Access are quite limited for formatting. What's the issue then?
In Ms Access everything is straightforward: declare a recordset, load it, and use it.
But with VB.Net, my current setup involves four components:
Dataset, TableAdapter, TableAdpater Manager, and Binding Source.
My precise needs are:
There should be a macro-enabled VSTO word document (*.docm) that, when opened, prints the most recent record from a Bill (Query Name is Bills).
Additional requirements:
Feature No.1: I have a sales form within an Ms Access database. When a button is clicked, the VSTO Word Document must open and print the latest bill, then close.
Feature No.2: This functionality needs to be invisible—when viewing the document, the action pane should display a navigator with a default view of the last bill number, but also include general navigation controls like "|<< < > >>| >*" along with a print button to display that bill using the control.
I understand this explanation may be lengthy, but I wanted to clarify everything in detail. Thanks for your support.
With Hope,
Prabhakaran
Available VSTO add-ins have been reviewed. Previous attempts were evaluated, noting successes and failures. Screenshots of your work, including macros, can be shared via imgur. Please ensure no personal details are disclosed in the forms or bills.
At first I focused only on the mail merge feature, but the issue is you can't hide the query dialog before merging the document.
Why VSTO?
Evolution!
I’d like to clarify how VSTO simplifies this. It saves a lot of code, resulting in fewer lines and quicker outcomes.
Then I need to grasp the Database ideas (especially read-only Binding) in VB.Net — from pulling data from a table to showing it on a control. I want to see both the design time and runtime perspectives to get the same result. I truly believe at least one person should have mastered this. Either this post needs to reach him or the reader must read it. I hope so. Let’s wait and observe...
The concern is that this forum isn't really a teaching platform. I've already tried various approaches, and likely someone else can help identify the issue. However, it would also need detailed database design information from your setup. (MS Access is my preferred tool)
And - with a bit of curiosity about:
"At first I was focusing just on the mail merge function. But the issue is you can't hide the query dialog before the document is merged."
What dialog box is this? What is its purpose?
Details? What process is being followed?
Screenshots? Share them via imgur (www.imgur.com).
I expect to see examples of what should appear and what actually shows up.
My concern is there might be a mistake in the logic or the code.
[Note: I would also consider using MS Access.]