Click here to Skip to main content
15,073,911 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Seek for Help.
Hi guys, I have some question regarding VB 2019 RDLC report sharing from server to the client PC would like to ask.

I am creating a setup file for my vb form and install it locally, everything works perfectly on my local pc.
Now I share the .exe to the local client PC, the client PC can access it with no issue. My RDLC reports also viewable on my client side. But when my RDLC report set a reference to assembly on my server side, my client pc become not visible to the RDLC report. Why?
Imgur: The magic of the Internet[^]

Imgur: The magic of the Internet[^]

What I have tried:

1. manually drag the .dll file to the .exe file location, but no work
2. manually add the .dll assembly file while creating the setup, but no work
3.remove the report reference, it works <<< but I want to use the report reference in order to generate barcode
Posted
Updated 4-Jan-21 20:26pm
v3
Comments
Gerry Schmitz 4-Dec-20 23:52pm
   
You think "System.Drawing" is the .dll related to you RDLC issue? It isn't.
Soh Chem Seng 5-Dec-20 0:51am
   
Hi thanks for reply
What i had tried to find the problem:
1. I remove the reference assembly from RDLC, the client PC is able to access the Report
2. I add again the reference to RDLC and copy the application shortcut, the Client Pc will auto shutdown my application

So i think the RDLC reference is the problems which is main cause, but i have no idea how to pass the Report reference assembly from server side to client side

1 solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900