I am currently using Microsoft Date and Time Picker Control on my Excel file and it works fine on my computer. But when I send it to someone, it says they're missing the file.
My question is whether it is possible to install it for the user
automatically so it does not say the control is missing from their
computer?
This is for a school project that maximizes the user experience, therefore I would need it to be simple and easy to setup.
Related
I have a device operated via Excel through com ports with MSComm32. Some macro linked to buttons on Excel forms used to make this device work properly. Up to these last days when it suddenly stopped working.
After some investigations, it seems there are some security considerations applied within Excel. The Excel file used up to now does not work anymore if Excel is runs as a standard user. An error message indicates the control cannot be created when trying to enter the creation mode, for example. But, if Excel is run as Administrator, then everything works fine.
Is there an easy way to fix this? For example granting access rights to standard user for the module MSComm32 OCX?
Thanks!
I am new in vb.net programming. Am facing a problem in database handling. Am using oledb to deal with database, which is MS Access in my project. I am dealing with queries at the time. Now the problem is that my queries are working well on vb form but are not affecting the actual database. For example, when am adding a record, it displays 'record added successfully', the message I have used for my conformation, but the actual database is not displaying the record I just entered and even got the above conformation message as well. I have checked query in sql editor too, its doing well. I have checked locals in vb debug mode, all are containing correct values.
Am not getting what's the reason behind that. Why it is displaying the success message but not modifying the actual database. Same is the case when am firing delete query, till now. I have not tried Update query yet.
Technology - Visual Basic.net with MS Access
Am using Access 2007 and Visual Studio 2013
Please Help by your suggestions
Do the controls on your form have the correct control source, i.e. the database table/query from and to which it should be reading and writing to?
Basically the problem was the gap between my understanding and .Net's working.
Here is the solution.
You can include database in two ways:
1.Either importing it directly to your project from the place, for example using drag and drop, or some other such method.
2.Or, by including it via using wizard.
But, the difference lies in connection string you use in your project, if you give absolute path of database, then you will directly see the alterations in database you have done using your application, even in testing and debugging mode via IDE.
connection.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\xyz.accdb"
But if you are using connection string provide by wizard, for example,
connection.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\xyz.accdb"
what the IDE will be doing is whenever you will be running project for debugging or testing, every time, it will copy the actual database, with its contents as well, in /bin/Debug folder. So, the changes you are performing will only be visible to that copy, not the actual file. So, if you want to verify with the database, like in our case, check the copy of database, which will be present in /bin/Debug folder. You will see the changes there. But, every time you run project for debugging, it will replace that copy with original one.
So, actually I was checking the original database file, not that copy, since the changes were only made to that copy. So that is why I was facing the above problem, not due to any programming fault.
I have run into an error with an Access Database created in MS-Access 2003. It's known the Calendar Control was deprecated in Access 2010 but unfortunately we need to keep using it. As a temp fix (until we can change to the date picker) we restored the MSCAL.OCX file on all 2010 users.
The issue:
We have a form to print schedules from a date range (using the calendar control). There is some VBA code to check to dates etc to make sure the range is accurate etc.
Everything works fine in 2003 but in 2010 the dates get selected fine on the form, is passed to the report (a print preview) fine as it displays in the footer BUT the query ignores the date range and prints ALL records (not just the records in the date range).
Is there any way I can step into Print Preview button when clicked to see what's being passed?
Any other ideas?
The issue with the filter not being applied to the report is a known Microsoft issue with certain set ups of Windows 7 and Access 2010. The hotfix found here: http://support.microsoft.com/kb/2596496 solved my problem.
I run Windows 7 64 bit and Office 2010 32 bit, when downloading the hotfix I selected the "x86" platform as that's the 32 bit. If you are using Office 2010 64 bit you should download the "x64" platform.
To find out your office version, open any office product, click File Tab, click Help and it will be on the right under "About Microsoft ".
The only way you can really do that is if your report/query is running some VBA code and put a Stop on the the VBA.
If your query is referencing the fields directly (IMNSHO a bad practice, but I'll work with what we've got) you could change them so they instead reference a VBA function that returns the results of those fields instead. Then you know what it is getting for sure.
There is one more trick that surely worked out for me as a solution, before I came across the accepted answer about hotfix on this thread. Also, because, the hotfix link leads to a valid thread, but there are not downloadable files.
The workaround:
Make a copy of the report file. Use that name in VBA under DoCmd call. Strange how it works, though. Such is the nature of bugs, I guess.
So I have this Access Database Project file that I have been tasked to edit. I have Access 2003 and 2007 installed. The ADP only supports 2003 for some reason. Anyway, the issue I have is that I can't figure out how to get to the VBA code in behind things.
The previous developers have done a very good job of locking everything down on the GUI such that the only thing I get when I open the application is a notice saying that it can't find the database on the server. (More than likely there is a problem there too, but since I can't look at code I don't know for sure.)
Does anyone know how to get around the GUI lockdown that has gone on here?
Michael
As it turns out, you can edit an ADP file that has all of the form information turned off by finding the file using Windows Explorer by highlighting the file, then hold shift, and then hit enter. You continue to hold shift until the interface is loaded.
I am about to release some reports in Access 2007 and I need to lock down the Queries so that no one can change the queries does any one know how I can do this in Access 2007?
Please Note: Simply adding a GUI and hiding the "database window" is not enough as people can still get in with the right key stroke etc.
You could Make an .ACCDE, and give that to your users to execute.
You can create an .accde file from an
.accdb file by clicking Database Tools
on the Office Fluent Ribbon, and then
clicking Make ACCDE. When you create
an .accde file, Access compiles all
the code in the database and strips
the editable version of the code from
the new .accde file. This process both
reduces the size of the resulting
database and guarantees that no one
can change the original source code.
When you open an .accde file in
Access, the form and report designers
and the Visual Basic Editor are not
available. In addition, you cannot
transfer forms, reports, and modules
to another database by export or
import.
However, since an ACCDE is apparently less secure than its predecessor the MDE, your best bet might be to convert the database to Access 2003 format by using the Save As command, and making an MDE from that. If you open an older .mdb file in Access 2007, a Make MDE command appears on the Database Tools tab instead of the Make ACCDE command that appears when you are working in an Access 2007 database.
In Access, if you click the Windows button and then Access Options, then Current Database, you will see options to disable navigation and keyboard shortcuts.