# Which Clarion Version to use for Production with MSSQL

**URL:** <https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780>\
**Category:** questions\
**Tags:** mssql\
**Created:** [November 15, 2023, 7:49pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780 "2023-11-15T19:49:23Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nardus\_Swanevelder](https://clarionhub.com/user_avatar/clarionhub.com/nardus_swanevelder/32/1066_2.png) [@Nardus\_Swanevelder](https://clarionhub.com/u/Nardus_Swanevelder)\
**Post date:** [November 15, 2023, 7:49pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/1 "2023-11-15T19:49:23Z")

</div>

Hi

I have been away from Clarion for about 4 years. I was just wondering which version of Clarion you are using for your production system. This will be for a Windows application that uses an MSSQL database. I am using third-party templates from CapeSoft, IngaSoft, Icetips and a few smaller ones.

Thanks

Nardus

---

<div class="post-metadata">

**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\
**Post date:** [November 15, 2023, 7:54pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/2 "2023-11-15T19:54:02Z")

</div>

Latest release - v11.1.13845  
If you have a choice, I do not believe there is any reason to not be current.

---

<div class="post-metadata">

**Author:** ![KenShauvin](https://clarionhub.com/letter_avatar_proxy/v4/letter/k/b9e5f3/32.png) [@KenShauvin](https://clarionhub.com/u/KenShauvin)\
**Post date:** [November 17, 2023, 4:45pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/3 "2023-11-17T16:45:24Z")

</div>

> [@totalhip](#):
>
> v11.1.13845

Stay away from Clarion v11.1.13845. It’s a recent release and it has too many bugs to be considered for live production applications. It’s basically, not useable. Use Clarion v11.1.13815 instead.

---

<div class="post-metadata">

**Author:** ![totalhip](https://clarionhub.com/user_avatar/clarionhub.com/totalhip/32/1477_2.png) [@totalhip](https://clarionhub.com/u/totalhip)\
**Post date:** [November 17, 2023, 5:05pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/4 "2023-11-17T17:05:57Z")

</div>

Surprised to hear. I haven’t yet hit anything serious in v13845 that was not in v13815.

---

<div class="post-metadata">

**Author:** ![seanh](https://clarionhub.com/letter_avatar_proxy/v4/letter/s/4af34b/32.png) [@seanh](https://clarionhub.com/u/seanh)\
**Post date:** [November 17, 2023, 10:29pm UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/5 "2023-11-17T22:29:11Z")

</div>

Actually it fixes a few bugs for me. I’m using it in production now.  
Haven’t had any problems as yet.

---

<div class="post-metadata">

**Author:** ![vitesse](https://clarionhub.com/user_avatar/clarionhub.com/vitesse/32/837_2.png) [@vitesse](https://clarionhub.com/u/vitesse)\
**Post date:** [November 18, 2023, 1:02am UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/6 "2023-11-18T01:02:30Z")

</div>

What problems have you had in v11.1.13845 Ken?

> Use Clarion v11.1.13815 instead.

I thought there were memory leaks in 13815 that were fixed in 13845?

---

<div class="post-metadata">

**Author:** ![Bruce](https://clarionhub.com/letter_avatar_proxy/v4/letter/b/ccd318/32.png) [@Bruce](https://clarionhub.com/u/Bruce)\
**Post date:** [November 18, 2023, 4:17am UTC](https://clarionhub.com/t/which-clarion-version-to-use-for-production-with-mssql/6780/7 "2023-11-18T04:17:14Z")

</div>

Im aware of 2 issues

1. libmaker doesnt run. (I just run an old one)

2. the “driver options” button in the dict editor crashes the ide. (Thats serious but doesnt impa t running programs)

If there are other issues, feel free to chip in.