|
use OpenFileDialog Control. this will allow you to choose any file.
You can get file name using OpenFileDialog.FileName
|
|
|
|
|
OpenFileDialog control seems to be the only option for you as it can allow users to choose any file from whatever directory path they want to access.
|
|
|
|
|
|
hi
i have error when i run my c# program.
the error is :
The Microsoft ACE.OLEDB.12.0 provider is not registered on the local machine.
and i have access 2010 on my laptop.
what is the solution for this error ?
|
|
|
|
|
Install JET[^]. Make sure you install the correct version; you'd want the 64-bit version if your CPU (and app!) support it, otherwise the 32-bit version.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
i have the correct version in my laptop.
my laptop has 64bit cpu and i have install access 2010 64 bit
|
|
|
|
|
..and your app? Set to 64-bit?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
yes my c# that i use in visual studio 2010 is 64bit.
Basically the error is not my laptop in my laptop run ok.
but when i try to run my c# setup program in another laptop
that is also 64 bit appears the error message that i said in my previous message.
Also we have the same programs access 2010 in 64 bit cpu.
i don't understand what maybe be the problem..
|
|
|
|
|
The problem is bitness.
Either the target machine doesn't have 64-bit ACE (Access) installed, or your code is running as 32-bit, not 64. You cannot mix 32- and 64-bit code in the same process.
You have to match the ACE bitness to your application, or the other way around. If the target machine has 32-bit Office (Access) installed and your app is compiled as x64 or AnyCPU running on a 64-bit machine, you'll get this message.
If your code is compiled x86 only and there is only 64-bit Office (Access) installed, you'll still get this error.
|
|
|
|
|
Huh?? There is no 64-bit version of JET. It's 32-bit only and was replaced by ACE. ACE comes in both 32- and 64-bit flavors.
|
|
|
|
|
Didn't know, thanks for the info
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
If you are using Visual Studio 2010, then the issue should not arise. Maybe some of the files are corrupt and that is causing the problem.
|
|
|
|
|
Hi
Thanks all for your help.
I found the problem rely on your advice.
I changed the target platform from configuration manager to x64 bit and the problem solved.
thank you again!!
|
|
|
|
|
Hi
It was printed with a barcode font, but
Scanner can not read it
There are special rules for barcode printing
Please advice please
Chab should the photos or conventional
Thank
|
|
|
|
|
|
First of all, you should learn that there are many barcode formats. And barcode readers may need to be configured to read your format - it is not advisable for a barcode reader to beconfigured to read any format any time, as the error rate is likely to increase. Configure the really required format only.
|
|
|
|
|
I have to deal with barcodes a lot, just not from a programming stand point. We exclusively use 3of9 as the format. With 3of9 you must have a leading * and a trailing *. Those are the starting and ending points for the software to read the barcode.
I am sure other formats are different, just research your format.
|
|
|
|
|
|
Depending on the ink, paper, and barcode size, the ink can spread after printing, making the barcode unreadable. This phenomenon is called "dot gain".
The way to correct for it is "bar shaving"; you remove column(s) of pixels at one or both edges of the bars to make them narrower. For 2D and GS1 barcodes, which have both vertical and horizontal dot gain, you can do bar shaving in two dimensions. (This is also called "erosion"; an operator from mathematical morphology). This is the mathematical inverse of dot gain.
|
|
|
|
|
hi
i want to make a setup of my c# project that i create on visual studio 2010 and use access database (for some reasons), but i don't know how i create to run on a server.
thnx
modified 28-May-13 10:51am.
|
|
|
|
|
There is no difference between creating a setup that runs on a workstation or on server. It's Windows in either case and everything still works the same way between the two editions as far as a Setup is concerned.
|
|
|
|
|
I do not think that that's a problem of the setup: You'll need a Windows Service instead of a Windows (GUI) / or Console application. That means some bigger changes to your project.
|
|
|
|
|
what can i do for this problem so that i manage to run my program
through the server ??
|
|
|
|
|
You're going to have to define exactly what you mean by "run the program through the server".
Are you placing the executable and all related code in a share on the server and client machines will launch it from there? Are you saying that you want the client machines to remote desktop into the server and run your app on the server? ...??
|
|
|
|