VB.NET and design-time dataset generated control

Hi,

We have recently taken over a maintenance project of VB.NET

One of the modules has around 7 forms and each form will print one report.
So there are 7 report design files.

Now consider Form1:CustomerDetails. This has a dataadapter control placed at
design time. The data adapter control has name of stored procedure defined in
the property SelectCommand. Stored Procedure as "GetCustDetails". Also
TableMappings property is set. Now from this dataadatpter, dataset is
generated at design time. This creates a file called dsetmain.xsd and it has
the structure of the stored procedure output i.e. the fields of stored
procedure. In this .xsd file, one field is manullay added called "Select"
which is of type boolean and does not belong to the table or stored
procedure. This form1 prints Report1 which also has data adapter and uses the
same stored procedure as above and also uses the dataset control at design
time.

Now consider Form2: SupplierDetails. Same flow as above except that Stored
Procedure is different. Now this creates another entry in dsetmain.xsd. The
..xsd file remains the same.

In this fashion, there are 7 entries in one .xsd file - one for each form.
This is how the earlier programmer has coded it. Now when the project is
compiled, it creates file called dsetmain.vb.dll in the debug folder -
ofcourse the regular binaries are also created. When we deploy the binaries,
even without this dsetmain.vb.dll, the application works fine.

Now when we took over the maintenance, we got change request to add one
additional field to Form1. We added this field to the Select statement of the
stored procedure. Then we deleted the existing dsetmain on form1 and
recreated and added to existing dsetmain.xsd. We could see the new field in
the grid of the form and also in the report that this form calls. I compiled
and copied the binaries (without dsetmain.vb.dll) on another machine on the
same network for testing. All fine.

Now I sent the binaries to the client. We found that my client cannot see
the additional field. What more ... other forms also stopped working. We
could not understand why this field is not seen at out client's place and
also why other forms stopped working. After spending 2-3 days, I applied a
workaround solution. Not too sure if I am doing the right but I deleted all
the entries from the .xsd file. I deleted the dataset object (dsetmain) from
all forms and reports. I then regenerated the dataset on each form and report
using the data adapter control. Now when I sent the binaries to the client,
application started working. Now this has been going on for 2 months.
Everytime a change request comes, we see everything on our dev machine and
test machine. But on our client machine it does work until we delete all
elements of .xsd and regenerate it.

Why does this happen? I also tried sending the dsetmain.vb.dll to the
client. Nothing happens until I delete complete xsd and regenerate. This is
time-consuming. Is there any way I can do something without regenerating the
..xsd? Why does other forms stop working when I modify only one stored
procedure? How does it affect other forms with different stored procedures?

Please help.

.

Relevant Pages

  • Can sub-report parameters vary by main report values per page?
    ... I have a main report that prints one client per page, ... Inside the main report are two sub-reports that derive three parameter ... The main report and the sub-reports each use an individual stored procedure ...
    (microsoft.public.access.reports)
  • Re: Where to find info/samle code to draw graph in Access Form using MS Graph
    ... the chart won't changed from client to ... > procedure and pass the clientID to the stored procedure. ... In a report the MasterLink and ChildLink properties control that, ...
    (comp.databases.ms-access)
  • SOLUTION: Reports in ADP based on stored procedures; child rowset error
    ... I have a report that is based on a stored ... Then I just set the report's RecordSource ... Then I had to add a second parameter to the stored procedure. ... RecordSource property from my ADP report into the immediate window, copy it, ...
    (microsoft.public.access.reports)
  • SOLUTION: Reports in ADP based on stored procedures; child rowset error
    ... I have a report that is based on a stored ... Then I just set the report's RecordSource ... Then I had to add a second parameter to the stored procedure. ... RecordSource property from my ADP report into the immediate window, copy it, ...
    (microsoft.public.access.adp.sqlserver)
  • Re: inconsistent report problems
    ... adParamReturnValue parameter. ... Is this field associated with a control on the report or with the Sorting ... @Counties VARCHAR to something smaller. ... set the record source of the report to the stored procedure, ...
    (microsoft.public.access.adp.sqlserver)
Loading