visual basic Sql query runs on developement pc, not other - sql

I am facing a strange issue, I have an old large VB6 app with datareports. It's large, so please don't suggest migrating etc.
I have a datareport on it which filters by date. the report works well on development PC but shows
"no value given for one or more required parameters"
or
"item cannot be found in this ordinal"
on all other PC's. This is quite strange as i have all the files.
Any known similar problem..

For anyone having a similar issue, i found a solution..so this may help in future.. the issue is purely bcoz the database is in the program files folder on non development machine and so full rights are not available to the app.. Try changing the db location outside program files and it'll all be perfect..

Related

VB.Net Website project returning errors which are not errors when I try to build it in vs2019

I made some changes to a VB.Net website project in Visual Studio 2019, and then I merged them into the UAT project in TFS, so that they can be published to our UAT site. When I try to build the project the Error List contains one item stating:
Maximum number of errors has been exceeded.
When I look at the Output tab I can see a long list of errors, but when I investigate them they are not errors at all. Some of the messages indicate syntax errors, but when I view the code nothing is highlighted and it all looks fine. Some of them say that a variable has not been declared, but it has. I also get Character is not valid errors - but again nothing is highlighted.
I should say that none of these errors is in any of the files I have been working on so they should be the same as the code which works fine on the UAT site. I already tried deleting the .vs folder and removing related folders from the Temporary ASP.Net Files folder, which fixed some issues I was having earlier, but not these errors.
I don't want to rant, but I feel like if Microsoft had a better testing regime there would be less of these sorts of issues and developers wouldn't need to waste so much time trying to work around their mistakes. I'm completely stuck at the moment so any suggestions would be gratefully received.
I wish I could say I know how to fix this but I don't. All I know is after a mixture of visual studio restarts, failed publishes, and a couple of fixed references the project now compiles and even publishes.
That would've been a lot easier and less stressful if visual studio provided more accurate error messages

api-ms-win-core-winrt-string-l1-1-0.dll is missing

Im using widows 7 on my working PC and i know i should update (i have win10 on my common pc)
but i still need to finish some important art projects and updating my system now would cause me a lot of compatibility trouble with some wierd and old programs i use so im stuck with win7 until im done with theses projects.
However, last night i had an update (i thought there was no more updates wor win7 Oo')
and since then, my mouse software wont work anymore !
the software is called "Steelseries Engine"
i worked until late and the software was working, but today, it wont start.
i tried to restart, update, and reinstalling but the problem seems to come from some missing dll.
when i go into the install folder and launch it from there, it gives me the following error :
the program cant start because "api-ms-win-core-winrt-string-l1-1-0.dll" is missing.
Anyone could tell me how to repair that ? is it something related to visual c++ or something ?
I really need help, because i have to finish my project fast and witout my mouse setup/macros its going to take ages.
art
Thanks a lot.
I have got the same problem from yesterday, now.
Same message, same circonstances, "steel series" connected + windows 7, and i see no reason why it started. i reinstalled the steelseries engine exe i kept from my personal depository file, and it worked, then today i rebooted the PC and the dll message came back. Very strange. Stranger is that the steel series engine exe for the mouse and Co is not available for windows 7 anymore ont the steelseries website, it is written "For windows 8 and upper versions."
edit: i fixed the .ddl missing trouble, even though i don't know how it started. Thanks to CCLEANER, i found in the start list a long command line stating that the .dll will be deleted by a steel series operator. Delete this useless line (i don't know where it suddenly came from, may be a corrupted auto upgrade by SSeries) and reinstall steelseriesengine. I'm pretty sure this problem had nothing to do with W7. Enjoy.

How to debug a compiled access database (accde)

I have an access front-end that connects to SQL Server tables and works fine. When I compile it into an accde file however, I get various errors when closing the DB. The errors seem to indicate that the program is still looking for a table or the value of a global variable. There is a routine in the Form_Close() event of a hidden form that Deletes all the links to the SQL Server back-end. So, how can I debug an already compiled access database? Why does the compiled DB behave differently than the uncompiled (accdb) version?
You need to trap errors using On error goto LabelName or if you don't care about errors you should use On error resume next on top of your code. You should still post your code to get more accurate help.
Are you talking about the same computer, or different computer?
The compiled accDE are VERY sensitive to being executed on a different machine (even the same version). The reason for this is that the compiled accDE takes on your current office release version.
In terms of global variables, and error handling?
accDE's are the BEST choice, since un-handled errors does not re-set local, or even global variables. In effect, a accDE runs like a un-stoppable freight train.
if your accDB (un-compiled) works and runs fine on your computer, then I have NEVER seen a case in which the accDE does not run, and in fact run better and behavies far more ro-bust.
So, no, you can't debug the accDE, but you can the accDB on the SAME computer.
If you are running the accDE on a different computer, then you left out a massive, huge and SPECTUALAR bit of information in your post.
If you ARE running the accDE on the same computer (that you created it with), then about the only possible is that the accDE file extension is using a different version of access to run with. This is rare - I would thus from the control panel, applications and features find your version of access and right click and do a repair on your office install.
The issue of patch version of office/access is VERY significant here. The reason of course is that if you deploy the accDB, it will often work because access can (and does) detect that the current version (even SP/patch/update) level of Access is different, then it can re-compile the code on the fly (because the accDB has the source code). The accDE does not, and thus it can't re-compile. However, I still STRONG suggest you deploy the accDE and resolve the SP/patch level issue since a accDE is oh so much more reliable in its operations compared to un-compiled accDB's.
I would be rather stunned if you are experiencing this issue on the same computer running the accDB and that computer is then used to create the accDE. If this is the actual case, then I would create a new blank accDB, and import everything from the old accDB, and then ensure it can compile the code (from IDE debug->compile). If the app compiles, then create the accDE, and it should work just fine. So, if this is same machine, then your accDB is damaged or corrupted. As I stated, create a new one, import everything from old, and create your accDE from that. It will work, and I never seen a case in which a accDB works, and a accDE does not work (on same machine).
1st thing to do is to decompile your application ...just Google Ms Access Decompile.
When you perform the Decompile and try to compile is almost certain that you will find some "forgotten" mistakes.
2nd if 1st fails its time to implement a robust logging system...based on text file writing, in order to avoid dependencies just work low : https://learn.microsoft.com/en-us/office/vba/language/reference/user-interface-help/freefile-function.
If it still fails post back with more info.

MSCOMCTLocx registering but still showing as 'Missing'

I am using VBA hosted in a drafting program called MicroStation. I have been using MSCOMCTL for the last few years to use controls such as Tab Views and ListViews. I have come back from a work trip and found my home PC to have a Windows Updated and im assuming that its broken it as i have found many articles relating to similar problems.
MSCOMCTL will register and says it has succeed, but still shows as missing in the VBA IDE. Usually i can just use the regsvr32 command and it will work no problems.
I have researched alot and have found a heap of solutions, but none work for me. The main one seems to be to run.
regsvr32 c:\windows\syswow64\regtlib.ocx
But i cant find regtlib.ocx on my Windows 10 - 64 Bit PC.
With this VBA Program, the company where it is deployed is very restricted on what the users can do so im hoping to find an alternative to MSCOMCTL but still within VBA that i can somehow package / compile within my VBA file and doesnt need to be installed onto the PC. Either that or a solution to get the file working. I have been reading article after article and trying a heap of things over the past few days but nothing has worked. It seems at the moment that my best option is to redesign the forms without the Tab Control and List Views. But i find this crazy as they are microsoft files.
Thanks in advance!
So far i have tried the below (plus a couple more escape me at this time)
*Replacing MSCOMCTL.ocx with a downloaded version (backed up the original just in case)
*Replacing MSCOMCTL.ocx with a version installed with Office 2013, located under the program files x86/office/root etc.
*Registering MSCOMCTL in safemode to ensure it wasn't in use.
*Searching the C drive for regtlib.ocx as that has been known to fix it.
*I did find an alternative, but requires various files to be installed onto the PC which wouldn't work in this case with the company's restrictions
*I know this is not a new issue, but most of the posts are a few years old and their solutions (usually re-registering the file) have not worked for me.
Thanks everyone. Problem has been solved. It was a combination of a couple of things based on dbmitch's answer.
By unchecking the missing control, closing down the host program and rebooting. Then opening up the VBA file and searching for the "Microsoft Common Controls" and selecting it. Even though the text was the exact same as the "Missing" one it seems to have done the trick.
I did do that step, but didn't close down the program and start again in between.
Thanks for your help guys!

Visual Studio keeps looking for .resx files in the wrong place

I am working with visual studio 2012, and my problem occurs in a large, old winforms application solution when I try to compile the whole application (dozens of projects).
When I get the latest code from source control (Team Foundation Server) for the first time, and build the solution, it builds just fine the first time. Then, if I make any changes, a later Build/Rebuild, will sometimes (not always) result in lots of projects in the solution throwing the following error for some of its resx files.
Unable to create a manifest resource name for "Contracts\Templates\ContractTemplateDb.resx". Could not find a part of the path 'C:\Windows\system32\Contracts\Templates\ContractTemplateDb.vb'
OR
Invalid Resx file. Could not find a part of the path 'C:\Windows\system32\NeptuneForms\HelpForm.resx'.
The problem is that there is no reason it should be looking in C:\Windows\system32 for these files, as they exist fine (and did during the last build) in the local directory of the project! The random directory is not always C:\Windows\system32, sometimes it is a random directory of another project, or even in another branch.
This happens sporadically to some of our developers, frequently to others, and almost always to me, and it seems unrelated to the code we are writing, because when it happened, I rolled back all the changes we had made since it started happening, and it still happened.
There are two things I've tried, that had no success.
Recreate the entire solution, and remove and readd all resource files as though they never existed before.
Install all windows updates and get the latest updates to Visual Studio 2012
Nothing has helped, and I am at a loss. My next step is to upgrade to 2013 and hope for the best, but I'm afraid thats not going to help either.
Does anyone have any similar experience, or any ideas of other things to try? I'm pulling my hair out over this one...