- Welcome, Guest. Please login.
1
You've got Questions? We've got Answers! / Re: Using slSetRelNamedLocks
Last post by Fim - December 30, 2020, 05:06:42 AMThanks for the advice and instructions. But I have decided to go another way to solve my problem, and it has gone well
2
You've got Questions? We've got Answers! / Re: Using slSetRelNamedLocks
Last post by Fim - December 17, 2020, 05:33:56 AMHow about this in SQlitening.bas
3
You've got Questions? We've got Answers! / Re: Using slSetRelNamedLocks
Last post by Fim - December 16, 2020, 01:37:31 PMMany thanks. I should have read the manual better.
/Fim W.
/Fim W.
4
You've got Questions? We've got Answers! / Re: Using slSetRelNamedLocks
Last post by cj - December 16, 2020, 01:15:11 PMFUNCTION GetLockNames AS STRING
'connect and open database before call
LOCAL s1,s2 AS STRING, x AS LONG
s1 = slGetStatus(1)
IF LEN(s1) = 0 THEN EXIT FUNCTION
REPLACE $VT WITH "," IN s1
REPLACE $BS WITH "," IN s1
FOR x = 2 TO PARSECOUNT(s1) STEP 8
s2 = s2 + PARSE$(s1,x) + ","
NEXT
FUNCTION = LEFT$(s2,-1)
END FUNCTION
5
You've got Questions? We've got Answers! / Using slSetRelNamedLocks
Last post by Fim - December 16, 2020, 06:13:20 AMIs there any way to find out what locks I have made with slSetRelNamedLocks?
/Fim W.
/Fim W.
6
General Board / Re: slOpen memory leak
Last post by cj - August 03, 2020, 10:24:18 PMThough I have not had a problem, I am removing this change in case
ATTACH or push the databases handles may need slOpen. Better safe than sorry.
FUNCTION slOpen ALIAS "slOpen ...
IF thDab THEN EXIT FUNCTION '<--- add line in SQLitening.Bas and compile
ATTACH or push the databases handles may need slOpen. Better safe than sorry.
FUNCTION slOpen ALIAS "slOpen ...
IF thDab THEN EXIT FUNCTION '<--- add line in SQLitening.Bas and compile
7
You've got Questions? We've got Answers! / Re: Error Code 7 A malloc() f...
Last post by Fim - July 20, 2020, 10:53:07 AMThere is something wrong with this forum. Wise answers disappear. Recently, there was an answer that meant that a row would be added to one of the SQLitening programs. That answer has disappeared. What is going on?
/Fim W.
/Fim W.
8
You've got Questions? We've got Answers! / Re: Error Code 7 A malloc() f...
Last post by Fim - July 15, 2020, 05:49:07 AMcj,
Thanks for that information
/Fim W.
Thanks for that information
/Fim W.
9
You've got Questions? We've got Answers! / Re: slSelBind
Last post by Fim - July 12, 2020, 01:56:54 PMI previously received some wise answers to my question. But they have disappeared now that I should take up the matter.
Fim W.
Fim W.
10
General Board / Re: slOpen memory leak (slOpe...
Last post by cj - June 17, 2020, 07:20:37 PMFredrick,
I don't think it is a bug so I doubt it. That is up to Paul Squires.
Options:
1. Use slClose before slOpen.
2. Use IF ISFALSE(slIsOpen) THEN slOpen.
3. Don't call slOpen more than once without first closing.
4. Write a function or macro that replaces slOpen.
5 Add line IF thDab THEN EXIT FUNCTION like I did.
Fim,
Thank you for reporting this 4/1/2020 at:
https://sqlitening.planetsquires.com/index.php?topic=9756.msg26645;topicseen#msg26645
I don't think it is a bug so I doubt it. That is up to Paul Squires.
Options:
1. Use slClose before slOpen.
2. Use IF ISFALSE(slIsOpen) THEN slOpen.
3. Don't call slOpen more than once without first closing.
4. Write a function or macro that replaces slOpen.
5 Add line IF thDab THEN EXIT FUNCTION like I did.
Fim,
Thank you for reporting this 4/1/2020 at:
https://sqlitening.planetsquires.com/index.php?topic=9756.msg26645;topicseen#msg26645