MediaWiki to ASP Converter

About MediaWiki to ASP Converter

Convert MediaWiki table markup to ASP (Active Server Pages) format. Perfect for integrating wiki data into classic ASP applications and legacy web systems.

Key Features

• Multiple Output Formats: Arrays, ADO Recordsets, or Dictionary objects
• Header Support: Uses headers as field names in recordsets and dictionaries
• String Escaping: Properly escapes quotes for ASP compatibility
• ADO Recordset: Database-like structure with fields and records
• Dictionary Objects: Key-value pairs for flexible data access
• File Upload: Upload .wiki files directly
• Instant Preview: Real-time conversion as you type
• Copy & Download: Easy export options

How to Use

1. Input MediaWiki Table: Paste your MediaWiki table markup or upload a .wiki file
2. Choose Format: Select between array, recordset, or dictionary format
3. Review Output: The ASP code updates automatically
4. Copy or Download: Use the Copy or Download button to save your ASP code

Output Formats

• Array: Simple nested arrays, easiest to use for basic data
• ADO Recordset: Database-like structure with fields, supports iteration and filtering
• Dictionary: Key-value pairs using Scripting.Dictionary, best for named access

Example Conversion

MediaWiki Input:

{| class="wikitable"
! Name !! Age !! City
|-
| John Doe || 28 || New York
|-
| Jane Smith || 34 || London
|}

ASP Output (Array):

<%
Dim data()
ReDim data(1)

data(0) = Array("John Doe", "28", "New York")
data(1) = Array("Jane Smith", "34", "London")
%>

ASP Output (Dictionary):

<%
Dim data()
ReDim data(1)

Set data(0) = Server.CreateObject("Scripting.Dictionary")
data(0)("Name") = "John Doe"
data(0)("Age") = "28"
data(0)("City") = "New York"

Set data(1) = Server.CreateObject("Scripting.Dictionary")
data(1)("Name") = "Jane Smith"
data(1)("Age") = "34"
data(1)("City") = "London"
%>

Common Use Cases

• Legacy Systems: Integrate wiki data into classic ASP applications
• Data Migration: Convert wiki tables to ASP format
• Intranet Applications: Use wiki data in corporate ASP systems
• Content Management: Import structured data from wikis
• Reporting: Generate reports from wiki tables
• Database Seeding: Use recordset format for database operations

ASP Compatibility

The generated code is compatible with:

• Classic ASP (Active Server Pages)
• VBScript runtime
• IIS (Internet Information Services)
• Windows Server environments
• ADO (ActiveX Data Objects) 2.x and later

Working with Output Formats

• Array: Access with data(row)(column), simple and fast
• Recordset: Use rs.MoveNext, rs.EOF, rs("FieldName") for database-like operations
• Dictionary: Access with data(row)("Key"), supports named field access

Tips for Best Results

• Use array format for simple data structures
• Use recordset format when you need database-like features
• Use dictionary format for named field access
• Ensure headers don't contain special characters (they'll be sanitized)
• Test the output in your ASP environment
• Remember to set proper ADO constants when using recordsets
• Clean up objects (Set rs = Nothing) after use

Frequently Asked Questions (FAQ)

• Which environments can run the generated ASP code?

  The output is intended for classic ASP using VBScript on IIS. It should run on typical Windows Server installations that support classic ASP and ADO.

• Do I need to define ADO constants like adVarChar manually?

  Yes. In many classic ASP setups, ADO constants are not defined by default. You can either include the adovbs.inc file or define the constants yourself so that values like adVarChar resolve correctly.

• What if my table has more columns than 255 characters per field?

  The generated recordset uses a default length of 255 characters per field. If you expect longer values, adjust the field length in the generated code to match your needs before running it.

• Can I safely use this for production data migration?

  You can use the generated code as part of a migration or integration script, but you should review, test, and version-control it like any other production code. Always validate data and handle errors appropriately.

• Is my wiki data ever sent to a remote server during conversion?

  No. All parsing and generation are performed locally in your browser. Your MediaWiki table and the resulting ASP code are not uploaded or stored externally.

Privacy & Security

All conversions happen locally in your browser. Your MediaWiki data is never uploaded to any server, ensuring complete privacy and security.