Libraries

I‘ve taken libraries that were originally made in previous versions of paradox. I have successfully resaved them under paradox 9 with no syntax errors. Then I deliver them. Problem is when I try to reference the delivered library vs the source, I get an error that this file doesn‘t have any symbol table information. Anybody know why?

> when I try to reference the delivered library vs the source

not sure what you mean here

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

When I reference library.lsl it works fine, but when I reference the library.ldl (that was made from the library.lsl) it reports this file doesn't have any symbol table information..

ok, I get it.. so it originally came from 7 or 8?.. same BDE? same basic installation logic?

does it really really really have to get delivered, if it works as-is?

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

No. But it could if I didn‘t want somebody in my code. Another question. In paradox 9, using the method setWorkingDir("blahblah") doesn‘t produce any errors goes right through but doesn‘t actually change it. Nothing is open except the script it is in. The script closes right after statement. Worked under 8. Any ideas? Should this be a new thread?

c'mon, be realistic.. who wants to change your code after 20 years, and why are they still working there?

if not setworkingdir("here") then

   errorshow()

endif

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Could you create and use an alias instead of the working directory?

Their are a lot of objects that reference :Work: alias. You can't use removeAlias(), addAlias(), or addAliasPath() on :WORK:

The reason behind these problems is people need to upgrade to Windows 10. Since Paradox 8 will not run on these machines, I had to upgrade to Paradox 9. I've converted all the code that was written under previous versions for decades. There are a number of things that don't work the same way. We all know this is a bandaid.

By the way.

if not setworkingdir("here") then

   errorshow()

endif

NO ERROR to show

 Agrred,  I went through this same process in 2018.  The only difference is that I chose to switch from v8 to v11 because it did not make sense to change from a 1998 version to a 1999/2000 version.

Warning errors and try...onFail

ErrorTrapOnWarnings(Yes)

Try

  if not setworkingdir("here") then

   errorshow()

  endif

onfail

   errorshow()

Warning errors and try...onFail

endtry

ErrorTrapOnWarnings(no)

in reply to several things

:work: and nothing are the same.. if no alias, it is assumed to be :work:

did you upgrade the BDE to 5.x when you loaded 9, or are you still using 4.5x? that could be related, cuz your "files not seen" errors are not common.. so you're saying you can set WORK, and you don't see stuff, but if you make an alias, and pick the same directory, you DO see that stuff?

upgrading from 8 to 9/10/11 should be trivial, other than the visual.. there can be exceptions, of course, almost always usually minor.. I hope your "fixes" were minor, too

10 was the work-in-progress that got stopped when the BDE was deprecated in 2002.. 11 is 10 with the SP applied.. any version used, 9/10/11, is from 2000 or 2002.. the one thing different with p10/11 in Win10, vs p9 with Win10 seems to be related to printers, printer names, printer response, etc

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Using BDE 5.0 and compared 5.1. Same.

No I'm not having any file problems. Things are pretty much working. I can manually change working directory . The problem is my programs can't seem to change them anymore. I have the if then routines in my code. There is no errors acts as though it changed it but, no change. Am I the only one who changes working directories? No one else has brought this up? 

no, I don't change :work: on the fly, but I'm sure there are others who do.. the only thing I can think of, that would stop it, as long as it's actually there, is not having full read/write/create rights

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

No access problem. Like I said can manually change it. This is in a testing environment. Just me as a client with the database sitting on a NAS storage device. It‘s pretty frustrating, thought you remaining gurus would have a remedy. Thanks very much for yout time. Didn‘t know there was any work done on versions 9/10/11. Thought Corel was just upping their number with newer office packages. But obviously version 9 runs on windows 10.

Now I wondering if bugs like setWorkingDir() were looked at in 10 or 11 or?

I guess your saying some printer issues were addressed ?

there are no setWorkingDir() bugs in open or closed status, in Bertil's buglist

the printer issues are pretty much external, fixed by common dll, etc.. but other printer issues are created by win10, such as the way it creates super long printer names (paradox limit is 32 char)

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

every Corel Suite after 2002 has p11

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

I read somewhere that paradox puts the command into some sort of queue and makes you think it worked. I finally got it to work. It must be the very last line of code before endmethod. Not even an endif statement can be after it. Supposedly you can leave a form open by trapping for an eventID. I haven't tried that yet. This particular thing I was working on was just a script. Didn't used to be so touchie.