# MULTI ROW TABLE in latex

I have written the code below

\begin{table}[]
\begin{tabular}{|l|l|}
\hline
Type                  & Name                 \\ \hline
\multirow{2}{*}{Amp}  & Diclofenac           \\ \cline{2-2}
& Dexametasone         \\ \hline
\multirow{3}{*}{Tab}  & Acetaminophen        \\ \cline{2-2}
& Cefixim              \\ \cline{2-2}
& Acetylcysteine (NAC) \\ \hline
\multirow{2}{*}{Cap}  & Gelophen             \\ \cline{2-2}
& Azithromycin         \\ \hline
\multirow{3}{*}{Syrp} & Bromhexin            \\ \cline{2-2}
& Salbutamol           \\ \cline{2-2}
& Guaifensin           \\ \hline
\end{tabular}
\end{table}


and I have

\usepackage{multirow}


but there errors when I compile the file: LaTeX Error: Not in outer par mode

• the not in outer parmode error is unrelated to your tabular, or the use of multirow. You have the table environment somewhere that it is not allowed, but as you have shown no example that generates the error it is impossible to tell you what to change. – David Carlisle Feb 9 at 10:40
• I'm pretty new to latex and I am using a template. I drew the table by an online table generator. I don't know what should I send you to show the problem. But could it be because the table is not in the exact style which is defined in the template? – Nooshin N.Ragheb Feb 9 at 11:29
• it is almost always simpler to just type the latex table directly rather than use a generator, but you need to take a copy of your document and delete everything you can delete until you get a small document that generates the error that you can add to your question. You can almost certainly delete the tabular and just have an empty \begin{table} \end{table} and get the same error, for example. – David Carlisle Feb 9 at 11:52
• I did what you said(I delete all the stuff )and I just kept the table and the code runs with no error. so the table is ok. I check my code again . thanks – Nooshin N.Ragheb Feb 9 at 12:42
• to ask the question you should delete things while keeping the error unless you post what is causing the error, we can't help. – David Carlisle Feb 9 at 12:44