How to display image from the path in the server and client architecture...
-
Helo, I have application that using a server and client architecture. The application in the local machine is connected to the database in the server. The database has a table that store the path of the images. The path of the image is the path that exist in the server. If the application want to display the image from the local machine, it will try to get the path of the image. What I want to ask are: - Does the application take the image first then transfer to local machine, or it just pass the path of the image to the local machine? If it just pass the path, I think it will raise an error, since the image is not exist in the local machine. - How to cover the error? - Or how to solve it in order the local machine can display the image from the path that exist in the server? Learning .NET
-
Helo, I have application that using a server and client architecture. The application in the local machine is connected to the database in the server. The database has a table that store the path of the images. The path of the image is the path that exist in the server. If the application want to display the image from the local machine, it will try to get the path of the image. What I want to ask are: - Does the application take the image first then transfer to local machine, or it just pass the path of the image to the local machine? If it just pass the path, I think it will raise an error, since the image is not exist in the local machine. - How to cover the error? - Or how to solve it in order the local machine can display the image from the path that exist in the server? Learning .NET
your problem is having the following the solution. You should get the network path of the image file, no matter from which machine you are accessing the image. If you are using the FileSystemObject it returns you the network path of a file. This path should be stored into the database server. So, while accessing images from your database it returns u the network path of the image.
-
your problem is having the following the solution. You should get the network path of the image file, no matter from which machine you are accessing the image. If you are using the FileSystemObject it returns you the network path of a file. This path should be stored into the database server. So, while accessing images from your database it returns u the network path of the image.
1. Ooh, i have said wrong thing before. Sorry. The image path is in another client computer. The server just function as a database server. The image path is saved to database server from another client. Thus, the image is in that client computer. Does it affect anything to what I have said before? 2. Is the network path same with the shared folder? I usually store the path, like "C:\MyApp\Image\" to the database. How can I store the network path of the path in the client computer to the database? 3. I am using OpenFileDialog to retrieve my image, is the OpenFileDialog the same with the FileSystemObject? If not the same, how should I use the FileSystemObject? Thanks for your help. Sorry for having my bad English. Learning .NET
-
Helo, I have application that using a server and client architecture. The application in the local machine is connected to the database in the server. The database has a table that store the path of the images. The path of the image is the path that exist in the server. If the application want to display the image from the local machine, it will try to get the path of the image. What I want to ask are: - Does the application take the image first then transfer to local machine, or it just pass the path of the image to the local machine? If it just pass the path, I think it will raise an error, since the image is not exist in the local machine. - How to cover the error? - Or how to solve it in order the local machine can display the image from the path that exist in the server? Learning .NET
Hi, Actually, you'll need to create a shared on the server and store an UNC path (that is, \\SERVER\SHARE\file.jpg") in the server database. That should solve the problem. Regards, Serge (Logic Software, Easy Projects .NET site)