Comments
Sort by recent activity
Hi Matthew
That is exactly what I mean. Need to get my eyes and brain tested, seem to have a memory leak :oops:
Thanks,
Lee / comments
Hi Matthew
That is exactly what I mean. Need to get my eyes and brain tested, seem to have a memory leak :oops:
Thanks,
Lee
Hi I didn't ask you to support CHM. I asked you to enhance the output files for PDF and Word. I also asked for the last version of SQL Doc to support CHM. Quoted "I'm not asking for CHM to be reinstated, just for a bit more consideration regarding real world usage. Can you tell me which was the last version to support CHM, please?" Kind regards, Digga / comments
HiI didn't ask you to support CHM. I asked you to enhance the output files for PDF and Word. I also asked for the last version of SQL Doc to support CHM.Quoted"I'm not asking for CHM to be reinstat...
Thanks Dan, I can confirm version 10.7.3 has resolved my issues. / comments
Thanks Dan, I can confirm version 10.7.3 has resolved my issues.
Same here and reported it too. / comments
Same here and reported it too.
Hey @Dan_J Fixed in 10.10. [image] Many thanks. / comments
Hey @Dan_J Fixed in 10.10. Many thanks.
Hey @Dan_J Many thanks for the update and look forward to testing this out. Have a great weekend. Kind regards, Digga / comments
Hey @Dan_J Many thanks for the update and look forward to testing this out.Have a great weekend.Kind regards,Digga
Hey @Dan_J Thanks for the update and nice to know I'm not going mad. Have a great weekend. Kind regards, Digga / comments
Hey @Dan_J Thanks for the update and nice to know I'm not going mad.Have a great weekend.Kind regards,Digga
Hey @Dan_J Here's the script: DECLARE @entityTable TABLE ( CRMEntity_Id INT IDENTITY(1, 1) , EntityName NVARCHAR(250) NOT NULL , IsEnabled BIT DEFAULT 1 , IsEntityModelModified BIT DEFAULT 1 , EntityModelModifiedDate DATETIME2 DEFAULT '1900-01-01' , IsError BIT DEFAULT 0 , ErrorMessage NVARCHAR(250) NULL , LastRunTime DATETIME2 DEFAULT '1900-01-01' ); SELECT * FROM @entityTable AS ET; The nullability switch changes as well as the loss in columns with the above script. I just removed IDENTITY from the first column and it worked fine with no difference between Azure or on-premise, when I put it back in the issue occurs again. Remember, in Visual Studio 2019 this worked fine in both cases. Kind regards, Digga / comments
Hey @Dan_J Here's the script:DECLARE @entityTable TABLE ( CRMEntity_Id INT IDENTITY(1, 1) , EntityName NVARCHAR(250) NOT NULL , IsEnabled BIT DEFAULT 1 , I...
Hey @Dan_J Thanks for the follow-up. I can confirm the settings are the same as your screenshot and I have upgraded to version 10.6.12.20269. There's no change in behaviour. Kind regards, Digga / comments
Hey @Dan_J Thanks for the follow-up.I can confirm the settings are the same as your screenshot and I have upgraded to version 10.6.12.20269.There's no change in behaviour.Kind regards,Digga
Hey @Dan_J When I raised this issue, yes I was connecting using Azure with MFA. I just got your message about the connection, I changed connection to my local instance to see the expected output, then switched to another Azure SQL Server using SQL Authentication, and unfortunately the behaviour returns. So the common is a connection to an Azure Database, regardless of the connection being Azure with MFA or SQL Authentication. Kind regards, Digga / comments
Hey @Dan_J When I raised this issue, yes I was connecting using Azure with MFA. I just got your message about the connection, I changed connection to my local instance to see the expected output, t...