I have an access database with a great deal of VBA code and it has been working great until recently. Now when my code hits one of the two lines below the database crashes and restarts.
With Application.FileDialog(msoFileDialogFilePicker)
With Application.FileDialog(msoFileDialogFolderPicker)
The dialog box pops up to choose a file or folder, whichever is applicable, but I cannot choose the file or folder as the database restarts.
I am on a company computer working on a virtual machine. If I use the database on my local machine the code works just fine, but not on the VM.
Does anyone have any idea why this would be the case? Is there some type of permission issue that i should check? What kind of an update could have been pushed recently that would have caused this?
Related
I am running some windows application that has access table attached.
Now after instaling the application on some computer, I'm trying to
find that access table (to change some data manually or change the location of the database) and I cant find it anywhere.
the application works fine with the database so it has to be somewhere on the PC.
do you have any idea where can I find it?
Ok,
First of all, I want to make the disclaimer that aside from some HTML I have done very little programming in my lifetime. However, as necessity so often dictates, I am in dire need of some assistance with that very thing at this moment.
Our agency has a web site that is hosted by another entity, and that entity is forcing our hand in moving the content of that site onto one of our own servers. All content has been moved to the new server, and all database tables from the old database have been moved onto our internal SQL server. The site primarily consists of asp files, but there is one page that is aspx. The problem arises when taking the "old" database tables offline and testing the aspx page. Even though all instances of the IP address to the old SQL server have been changed to reflect the IP of the new SQL server, the aspx page insists on requiring the connection to the old database (the error indicates the tables are offline, thus pointing to the old SQL server). Everything else works as it should, and the "Web Application" has been designated as such in IIS.
I know I am missing something somewhere... but I just can't put my finger on it. Any ideas would be greatly appreciated. I'm starting to wonder if the reference to the old IP address is compiled in a file somewhere that I just can't find.
Thanks
Ok guys, I found my solution. For programmers, this solution probably would have been a no-brainer, but for others maybe not so much.
I have to give a pat on the back to "Creator" for pointing me in the direction of the project file. I wasn't sure that it was still available, but thankfully the programmer who designed this application somewhere a little over ten years ago was nice enough to leave it in the web directory with everything else.
What I wound up doing was as follows:
Opened the project file in Visual Studio 2010 and converted the project from 2003 to 2010.
Added the connection strings into the web.config to the new SQL server.
Right clicked on each item and excluded all of the old pieces to the application (in Solution Explorer) that were no longer needed.
Right clicked on the project and navigated to Package/Publish Settings > Package/Publish SQL and chose to "Import from Web.config".
Saved the project, then right clicked and "Converted to Web Application".
Right clicked and performed a "Build". I'm guessing this re-wrote the dll file.
Copied the directory and needed files back over to the web server and converted the directory in IIS to a Web Application.
Sat back and marveled at my success.
Thank you guys for pointing me the right direction!
I have a program that uses access database to store the information. The problem I am encountering is when I shared from my desktop and I go to another desktop it doesnt want to add a new record or the query that is appending the information is not working. It only works in the desktop that I ran the msi. Can anybody help me what I am doing wrong. I am not using remote desktop nor team viewer. I am not using remote services like remote desktop or team viewer. First thing I ran the msi and install the program in my desktop. Secondly I got to my c drive and share that forlder where the program lives. Third I go to another computer click on network and I look for my computer and go to that folder and run that application. Next I tried to test my program by adding a new record but it gives me a message there is no query to update this record. I go back to my desktop and it works find.
It's because the program is referencing to the location of the database on THAT pc you're running it to...
C:\ on your pc is not same C:\ on the other pc.
I'm having a massive problem trying to write a file into the c:\windows\system32 directory. The code works fine on 32 bit machines, however does not work on 64 bit machines.
My user account is an administrator on the machine, and even right clicking and choosing to run the app as administrator does not solve the issue.
When writing the file, no exception is thrown, but the file is not written.
I have read various posts regarding adding an app.manifest file containing the requestedExecutionLevel node to my solution, but as yet am unable to get this to work. I have a feeling this may be because I'm using vb.net rather than c#.net
Has anybody encountered this issue before? I'd be delighted if somebody could provide an example VS2010 VB.Net project with a correctly configured app.manifest file as I'm a little unsure whether my attempts at setting this up are correct.
(also, this is not a malicious app I am writing, I'm working on a version control app for our team and need to be able to interface with IIS files held in c:\windows\system32\inetsrv\config).
Thanks
David
Maybe the file is written under UAC Virtualization and located under C:\Users\Username\AppData\Local\VirtualStore\Windows\System32
Windows Blog - Tips on what is going on behind the scenes.
TechNet - Look under Data Redirection
Under Local Sercurity Policies there is the following option which controls UAC Virtualization.
I am trying to save an Excel 2010 file to a Sahrepoint 2010 document library but keep getting the error:
"You can't open this location using this program. Please try a different location"
Googling this suggests enabling "Desktop Experience" on the server which I have done. All Excel services are activated.
Has anyone come across this and been able to resolve successfully? I am wondering if this is more security related but the security set-up looks fine.
Any suggestions?
Thanks
I think that there are potentially a couple of things that could solve this problem depending on your set-up.
You are right that a lot of internet advice is to enable desktop experience, but if you are not running on the server or if you have already done this then one of the suggestions below could help.
This is only for dev environments however.
If you are running on the server and trying to use your app as admin then configuring IE ESC to turn off enhanced security for Admins should help
If you are running off server and have the issue and do not want to turn off IE ESC (on the server) for users then you need to enable a mechanism to allow auto-logon, either through integrated security (i.e. you are part of the domain), accessing through an anon web-site port on your SharePoint app (set-up anon web access in SharePoint) or set up and store a WebDav link and use that as the open/save URL.
My (unconfirmed) theory is that there is some auto-login going on in the background that hinders a streamlined office integration. Most of the time, SharePoint will be set up with Kerberos (not NTLM) or be in anon mode so enabling desktop experience if running on the server will be the best first step to try.
Hope this helps.
The problem is that the full path to the file is too long.
I had this problem with a PowerPoint presentation. The full path to the file was over 275 characters. When I shortened the file name to bring the full path under 250 characters, I was able to open the file normally.