I currently use visual basic 6.0 and in one of forms, I connected textboxes to the database(MS Access) using a data control. It worked perfectly fine but when I opened the program in the other computers and tried to call the form that has the data control, the message saying "Invalid path...." keeps coming up.
Can anyone provide any solutions for this problem?
Your problem only has three possible causes:
The path is not a fully qualified path. If you don't specify a full path (C:\blah\blah\file.txt or \\server\share\blah\file.txt), then it become a relational path to the current working directory. Unless your code specifies this, it is unpredictable. Solution: use a full file path or make sure your code switches the current working directory to where you need it to be.
The path is is not valid in any circumstance. Solution: Fix the path.
Users don't have access to the share/file. Solution: change security on the share/folder/file.
Related
Can someone please help me out with this? I tried using long path tool but they want me to pay in order to delete the folder. However I cant find the file the system is complaining about. I went to the folder
C:\Users\Casey\Desktop\Workspace\LegalHoldings\Sprints\Sprint5\Expunctions\LegalHoldings.Expunctions.Service.External\ServiceReferences\FillingReviewMDEService\LegalHoldings.Expunctions.Service.External.FilingReviewMDEService.GetFeesCalculationsResponse.datasource
This file:
FilingReviewMDEService.GetFeesCalculationsResponse.datasource
Does not exist in the folder?!?!?!
I don't know what to do, I have been reading a lot of work-arounds online however most people suggest using long path tool but I remember having this issue in the past but I cant remember how I solved. I believed it was something to do with the Developer Command prompt and resetting some paths.
All help would be greatly appreciated
In VS/TFS 2012, I found this helpful:
[Open TFS Explorer] -> [Right click the root folder] -> Advanced->'Remove Mapping...'
Then, you can change the path:
HTH
Usually these problems can be solved by shortening the paths higher up the tree.
It looks like your local path is the problem, so try mapping your code to a shorter root folder (e.g. C:\code rather than c:\users\Casey\desktop\workspace...)
Alternatively, you may be able to rename some mid level folders in your tfs structure to shorten the paths. But that's more extreme and probably not necessary in this case.
Not sure if you're even using the data binding features which the .datasource file is generated for, but turning that off in your service reference configuration by manually editing the .svcmap file would solve your problem.
After editing make sure you use the Update Reference feature to get rid of the unwanted file:
The second step would be to not map $/ to your user profile in your workspace mapping, but $LegalHoldings/Sprints/Sprint5/Expunctions to something like C:\Workspace\Sprint5 specifically that would drastically reduce the path depth required for your project.
If TFS still has a pending change for this file, you can use the tf utility from your workspace folder
C:\Users\Casey\Desktop\Workspace\LegalHoldings> tf undo $LegalHoldings/Sprints/Sprint5/Expunctions/LegalHoldings.Expunctions.Service.External/ServiceReferences/FillingReviewMDEService/LegalHoldings.Expunctions.Service.External.FilingReviewMDEService.GetFeesCalculationsResponse.datasource
to get rid of the pending change.
I'm using project.vim with VIm to manage large code bases with deep directory structures.
When I switch to another one or create (\C) a new one and do a refresh (\R) project.vim starts displaying messages through the whole process for different directories:
<dir_name> is not a valid directory. [O]K:
I have to press Enter all the time, although the directories exist. I took a look at the code and it checks if the path is a directory. They are.
Maybe there is a fix for this. The directories are under Perforce management, so everything is read-only.
I have to stay at the keyboard and keep pressing Enter for it to go to next directories... For large code bases this is takes a long time.
I contacted the author some time ago, but there was no response.
Did anyone encounter this before?
Could it be the it is bothered by the read-only-ness?
Is there a fix for this?
Thanks
The plugin uses glob() for some of those directory checks, which is affected by the 'wildignore' setting. Try
:set wildignore=
If that fixes the problem (and you have at least Vim version 7.2.51), you can modify the plugin's code to use glob(..., 1) instead.
The company that I am working at is still using visual foxpro, and I am doing a fingerprint scanner using vfp9 and Griaule Fingerprint SDK 2009.
Everything is doing fine during the first run of the program. But when I re-run it againg. The error will happen. Any ideas why I keep on having that problem? Missing GRFINGER.DLL.
It's getting hard for me to find any support today because foxpro application development is getting obsolete.
The rub of the problem seems to be that the first run causes Fox to be somehow unable to find the DLL or to load it. The latter can occur if the DLL itself is findable but one of its dependencies (like its C runtime DLL) is not.
This may be due to a changed search path (SET PATH). If the search path contains relative directories then a simple change of the current working directory changes the effective search path, even though the actual text (set("PATH")) remains unchanged. That can happen because of things like file open/save dialogues, for example.
P.S.: sorry for the belated answer - the question was at the top of the recent/active list because someone had edited the question recently, and only after posting the answer did I realise how old the question was. However, the answer might still be useful for someone with a similar problem.
I'm attempting to sync my local PHPStorm project from my Windows 7 PC with my Ubuntu server.
When I try any kind of connection (e.g. "Test SFTP connection"), it fails with
Invalid descendent file name "C:\nppdf32Log\debuglog.txt"
the folder mentioned doesn't exist on my Windows machine, and of course not on my Ubuntu server.
Even the most basic operation connecting to the Ubuntu server is failing because of this - Jetbrains support suggested asking here, so does anyone have a clue?
You have a file on your Ubuntu server with that C:\nppdf32Log\debuglog.txt name. YES -- it's on Ubuntu and YES -- it's actually a file name and not full path (Linux allows : and \ characters in file names).
Unfortunately such file name is invalid on Windows and library used for SFTP communications in PhpStorm does not allow to process such files in any way (yes, it's valid as full path but not as file name alone).
The solution is to connect to your SFTP using another program (e.g. FileZilla) and delete that file. After that you will be able to continue with PhpStorm built-in SFTP functionality.
P.S.
Such file is usually created by Firefox on Linux (google that file name for additional details).
https://askubuntu.com/questions/144408/what-is-the-file-c-nppdf32log-debuglog-txt
Jetbrains support suggested asking here
That's odd (and hard to believe for me) -- they should know about such issue for sure -- you are not first who is facing the same error.
In any case -- this is the ticket to watch after -- hopefully the used library (for SFTP communications) will allow handling such situations better in the future.
http://youtrack.jetbrains.com/issue/WI-2449
I met with the same problem,
but I included logging of errors (description here https://devnet.jetbrains.com/docs/DOC-1202)
and I saw that I had created a file with incorrect name
I had this same problem, but it was not due to Firefox and I wonder if the original asker might have made the same mistake I did in configuring his xdebug.
As a newbie, in setting the value for xdebug.remote_log in my php.ini (actually in separate xdebug.ini), I used the windows file path to my project on my local machine. Why? Because the value called "remote_log", so I mistakenly thought it wanted the path on my windows machine, which I thought was very strange at the time. But I am new to remote debugging, so... Oops.
Using windows path is wrong:
xdebug.remote_log="C:\Users\Buttle\PhpstormProjects\xdebug_log.txt"
And it results in:
/var/www/myproject/C:\Users\Buttle\PhpstormProjects\xdebug_log.txt
(the bolded part is the actual file name)
This is right:
xdebug.remote_log="xdebug_log.txt"
And presumably results in:
/var/www/myproject/xdebug_log.txt
(the bolded part is the actual file name)
It appears that Xdebug saves that log file inside of the folder where the requested php file came from (in my case, my project's index.php file).
I imagine that if I enter an valid linux path, I might be able to put the file somewhere else. E.g.
This might work:
xdebug.remote_log="/var/www/xdebug_log.txt"
So this solves 2 problems: 1.) why the heck doesn't xdebug log anything on its server (it does!) 2.) descendant file problem.
I am new to Tibco Business Events and facing a strange issue in BE 5.0. This is what I am trying to do:
I have created a DB concept named INVENTORYCONCEPT and have created a corresponding event for the same.
I have set this event as default destination in my JMS channel. Now when I am trying to create the instance of INVENTORYCONCEPT by giving command like ‘Concepts.INVENTORYCONCEPT inventory’ the BE studio gives me error that “INVENTORYCONCEPT is not the part of Concept folder” .
PFA the screenshot of my project files.
So can anyone tell me that what I have missed here ?
PS: I tried the traditional methods of restarting thr studio and changing the workspace.
You need to give some name to the concept instance that you are creating. What you are doing right now is
Concepts.INVENTORYCONCEPT = null;
This is wrong. You need to do something like this
Concepts.INVENTORYCONCEPT inventory = null;
Its always recommended & advised that you clean and validate your project when any changes are made to the project.
If the error still persists, you can open the concept using XML Viewer in BE and check the relative path of the Concept there. The reason for this to happen is when you create a concept in a some folder and later move it to a different folder, sometimes the XML related to that concept doesn't change (usually when you drag and drop the .concept file instead of using the Refactor option). You can just change the relative path in the XML and it should work.
Sometimes weird errors also occur when your workspace gets corrupted. In such cases, changing the default workspace and importing the project in the new workspace does the job.