1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder.
2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location?
2. Can you read from the debugger what is stored in variable 'lcAPPaddr'?
I have been installing the latest adapter and have a few comments:
1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder.
2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
-- thn (FoxInCloud)
It does not matter where I run it from, I did several re-installs and ran it from there, still cannot run.
lcAPPaddr = "AWADAPTER.APP"
probably not relevant, but the message after the install that is supposed to say what was installed successfully actually shows the VFP textmerge command, i.e. " .... 1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location? 2. Can you read from the debugger what is stored in variable 'lcAPPaddr'? 1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder. 2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
Hi Tuvia
I have been installing the latest adapter and have a few comments:
We have a hard time with this error because, while some (scarce) users have it, most others don't.
I hope you can help us fix it - so far we fail to understand what may be the underlying cause ...
Here is instruction where the error occurs:
DO (m.lcAPPaddr) WITH;
m.ltAPP; && awAdapter date-time
, m.loFrmConfig; && FAA form configuration
, m.loHTTP; && as wwHTTP of wwHTTP.prg
, Evl(m.lcURL, .null.); && foxincloud.com URL
, FoxInCloud_TIMESTAMP && FAS date-time litteral found in aw.h && awAdapter.prg vérifie cette date-heure pour, si nécessaire, forcer une réinstallation de ce lanceur
Given the error (1918 'file name is too long' [The name of the file exceeds current system capacities.]), the first culprit we can think of is 'm.lcAPPaddr' - in this case you just have the name of the app, "AWADAPTER.APP", located in curdir().
So the next idea is that VFP (or Windows) automatically adds the path to the file ('c:\users\username\appdata\roaming\Microsoft Visual Foxpro 9\ab\aw\'), and the full path to the file exceeds the NTFS limitation of 260 characters (http://msdn.microsoft.com/en-us/library/aa365247.aspx#maxpath).
In my case I have:
? len('C:\Users\ThierryNivelet\AppData\Roaming\Microsoft\Visual FoxPro 9\AB\AW\awAdapter.app') && 85
Even if my name was 'Gondrand de Mortefontaine de la Villardière' instead of 'ThierryNivelet', the length of this string would be 114, very far from the 260 limit.
Anything you can see in the debugger 'locals' window that be a hint?
Which OS do you use?
Actually, I had an old enough version of the adapter that in ran from home() + aw folder, which was the very original location way back when. So I had never seen it use home(7).
It does not matter where I run it from, I did several re-installs and ran it from there, still cannot run.
lcAPPaddr = "AWADAPTER.APP"
probably not relevant, but the message after the install that is supposed to say what was installed successfully actually shows the VFP textmerge command, i.e. " .... 1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location? 2. Can you read from the debugger what is stored in variable 'lcAPPaddr'? 1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder. 2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
Hi Tuvia
I have been installing the latest adapter and have a few comments:
-- thn (FoxInCloud)
First, home(7) should never be used with VFP, especially if it pointa to user\appdata etc. This is a source of several bugs in VFP, such as VFP caching copies of prg's there and then being unable to find them.
I am having more succes now and got as far as loading the adapter, it seems to appear correct, I will try an adapation and see.
FYI, for the adapter, here is what I did:
1. Downloaded the adapter from http://www.foxincloud.com/awAdapterSetup.zip
2. the file size is about 2.2 Mg.
3. unzipped the files and ran awadaptersetup
4. It says it installed but the message appears to be un-merged. image:
5. Said yes to run the adapter.
6. Previously this is where the errors occurred, now I have a message that says downloading version dated .F.
Hi Tuvia,
We have a hard time with this error because, while some (scarce) users have it, most others don't.
I hope you can help us fix it - so far we fail to understand what may be the underlying cause ...
Here is instruction where the error occurs:
DO (m.lcAPPaddr) WITH;
m.ltAPP; && awAdapter date-time
, m.loFrmConfig; && FAA form configuration
, m.loHTTP; && as wwHTTP of wwHTTP.prg
, Evl(m.lcURL, .null.); && foxincloud.com URL
, FoxInCloud_TIMESTAMP && FAS date-time litteral found in aw.h && awAdapter.prg vérifie cette date-heure pour, si nécessaire, forcer une réinstallation de ce lanceur
Given the error (1918 'file name is too long' [The name of the file exceeds current system capacities.]), the first culprit we can think of is 'm.lcAPPaddr' - in this case you just have the name of the app, "AWADAPTER.APP", located in curdir().
So the next idea is that VFP (or Windows) automatically adds the path to the file ('c:\users\username\appdata\roaming\Microsoft Visual Foxpro 9\ab\aw\'), and the full path to the file exceeds the NTFS limitation of 260 characters (http://msdn.microsoft.com/en-us/library/aa365247.aspx#maxpath).
In my case I have:
? len('C:\Users\ThierryNivelet\AppData\Roaming\Microsoft\Visual FoxPro 9\AB\AW\awAdapter.app') && 85
Even if my name was 'Gondrand de Mortefontaine de la Villardière' instead of 'ThierryNivelet', the length of this string would be 114, very far from the 260 limit.
Anything you can see in the debugger 'locals' window that be a hint?
Which OS do you use?
Actually, I had an old enough version of the adapter that in ran from home() + aw folder, which was the very original location way back when. So I had never seen it use home(7).
It does not matter where I run it from, I did several re-installs and ran it from there, still cannot run.
lcAPPaddr = "AWADAPTER.APP"
probably not relevant, but the message after the install that is supposed to say what was installed successfully actually shows the VFP textmerge command, i.e. " .... 1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location? 2. Can you read from the debugger what is stored in variable 'lcAPPaddr'? 1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder. 2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
Hi Tuvia
I have been installing the latest adapter and have a few comments:
1/ You probably have set('textmerge delimiters') != '<>'
(we should take this case into account though)
2/ not sure I understand 'downloading version dated .F.'
do you mean the file does not download or the message is wrong?
I apologize for the delay, I was unexpectedly called away.
First, home(7) should never be used with VFP, especially if it pointa to user\appdata etc. This is a source of several bugs in VFP, such as VFP caching copies of prg's there and then being unable to find them.
I am having more succes now and got as far as loading the adapter, it seems to appear correct, I will try an adapation and see.
FYI, for the adapter, here is what I did:
1. Downloaded the adapter from http://www.foxincloud.com/awAdapterSetup.zip
2. the file size is about 2.2 Mg.
3. unzipped the files and ran awadaptersetup
4. It says it installed but the message appears to be un-merged. image:
5. Said yes to run the adapter.
6. Previously this is where the errors occurred, now I have a message that says downloading version dated .F.
Hi Tuvia,
We have a hard time with this error because, while some (scarce) users have it, most others don't.
I hope you can help us fix it - so far we fail to understand what may be the underlying cause ...
Here is instruction where the error occurs:
DO (m.lcAPPaddr) WITH;
m.ltAPP; && awAdapter date-time
, m.loFrmConfig; && FAA form configuration
, m.loHTTP; && as wwHTTP of wwHTTP.prg
, Evl(m.lcURL, .null.); && foxincloud.com URL
, FoxInCloud_TIMESTAMP && FAS date-time litteral found in aw.h && awAdapter.prg vérifie cette date-heure pour, si nécessaire, forcer une réinstallation de ce lanceur
Given the error (1918 'file name is too long' [The name of the file exceeds current system capacities.]), the first culprit we can think of is 'm.lcAPPaddr' - in this case you just have the name of the app, "AWADAPTER.APP", located in curdir().
So the next idea is that VFP (or Windows) automatically adds the path to the file ('c:\users\username\appdata\roaming\Microsoft Visual Foxpro 9\ab\aw\'), and the full path to the file exceeds the NTFS limitation of 260 characters (http://msdn.microsoft.com/en-us/library/aa365247.aspx#maxpath).
In my case I have:
? len('C:\Users\ThierryNivelet\AppData\Roaming\Microsoft\Visual FoxPro 9\AB\AW\awAdapter.app') && 85
Even if my name was 'Gondrand de Mortefontaine de la Villardière' instead of 'ThierryNivelet', the length of this string would be 114, very far from the 260 limit.
Anything you can see in the debugger 'locals' window that be a hint?
Which OS do you use?
Actually, I had an old enough version of the adapter that in ran from home() + aw folder, which was the very original location way back when. So I had never seen it use home(7).
It does not matter where I run it from, I did several re-installs and ran it from there, still cannot run.
lcAPPaddr = "AWADAPTER.APP"
probably not relevant, but the message after the install that is supposed to say what was installed successfully actually shows the VFP textmerge command, i.e. " .... 1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location? 2. Can you read from the debugger what is stored in variable 'lcAPPaddr'? 1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder. 2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
Hi Tuvia
I have been installing the latest adapter and have a few comments:
-- thn (FoxInCloud)
The message is wrong - the message literally says "version dated .F.". Not that big a deal.
Hi Tuvia
1/ You probably have set('textmerge delimiters') != '<>'
(we should take this case into account though)
2/ not sure I understand 'downloading version dated .F.'
do you mean the file does not download or the message is wrong?
I apologize for the delay, I was unexpectedly called away.
First, home(7) should never be used with VFP, especially if it pointa to user\appdata etc. This is a source of several bugs in VFP, such as VFP caching copies of prg's there and then being unable to find them.
I am having more succes now and got as far as loading the adapter, it seems to appear correct, I will try an adapation and see.
FYI, for the adapter, here is what I did:
1. Downloaded the adapter from http://www.foxincloud.com/awAdapterSetup.zip
2. the file size is about 2.2 Mg.
3. unzipped the files and ran awadaptersetup
4. It says it installed but the message appears to be un-merged. image:
5. Said yes to run the adapter.
6. Previously this is where the errors occurred, now I have a message that says downloading version dated .F.
Hi Tuvia,
We have a hard time with this error because, while some (scarce) users have it, most others don't.
I hope you can help us fix it - so far we fail to understand what may be the underlying cause ...
Here is instruction where the error occurs:
DO (m.lcAPPaddr) WITH;
m.ltAPP; && awAdapter date-time
, m.loFrmConfig; && FAA form configuration
, m.loHTTP; && as wwHTTP of wwHTTP.prg
, Evl(m.lcURL, .null.); && foxincloud.com URL
, FoxInCloud_TIMESTAMP && FAS date-time litteral found in aw.h && awAdapter.prg vérifie cette date-heure pour, si nécessaire, forcer une réinstallation de ce lanceur
Given the error (1918 'file name is too long' [The name of the file exceeds current system capacities.]), the first culprit we can think of is 'm.lcAPPaddr' - in this case you just have the name of the app, "AWADAPTER.APP", located in curdir().
So the next idea is that VFP (or Windows) automatically adds the path to the file ('c:\users\username\appdata\roaming\Microsoft Visual Foxpro 9\ab\aw\'), and the full path to the file exceeds the NTFS limitation of 260 characters (http://msdn.microsoft.com/en-us/library/aa365247.aspx#maxpath).
In my case I have:
? len('C:\Users\ThierryNivelet\AppData\Roaming\Microsoft\Visual FoxPro 9\AB\AW\awAdapter.app') && 85
Even if my name was 'Gondrand de Mortefontaine de la Villardière' instead of 'ThierryNivelet', the length of this string would be 114, very far from the 260 limit.
Anything you can see in the debugger 'locals' window that be a hint?
Which OS do you use?
Actually, I had an old enough version of the adapter that in ran from home() + aw folder, which was the very original location way back when. So I had never seen it use home(7).
It does not matter where I run it from, I did several re-installs and ran it from there, still cannot run.
lcAPPaddr = "AWADAPTER.APP"
probably not relevant, but the message after the install that is supposed to say what was installed successfully actually shows the VFP textmerge command, i.e. " .... 1. From the very beginning, awAdapter installed in this location [Home(7)] ... did you try to run it from some other location? 2. Can you read from the debugger what is stored in variable 'lcAPPaddr'? 1. The adapter update install program installed awadapter.app in ab\aw under the users\username\appdata\roaming\Microsoft \Visual Foxpro 9\tools\ab. No option was given. That makes it only work for that user, and I would never store data there. It also has the icon set to that folder for "start in", and people work on the assumption when they start VFP they are in the home folder. 2. awadapterstart.app will not run, it gives an error file name too long in line 250. So now I am stuck - the old version insists on an upgrade and the new version does not work.
Hi Tuvia
I have been installing the latest adapter and have a few comments: