Database Viewer/Editor (xBaseView 6.1)

[mutex]

Main News: [+] - added

v.6.1.0.563 20.11.2005
[+] EXE-shell for plugin.
[+] Create DBF file.
[+] Create DB file.
[+] Create SQL "Create Table" operator.
[+] Import from CSV and TAB texts.
[+] Import from HTM file.
[+] Import from Microsoft ADO XML file.
[+] Import from Borland CDS XML file.
[+] Import from FoxPro DBF file.
[+] Import from Paradox DB file.
[+] Export to primitive XML format.
[+] Export to Paradox DB file.
[+] Append Mode for export.
[+] Export/Import memo fields.

Description:

xBaseView - Universal Database Viewer (and Editor)

View and edit files:
1. FoxPro (*.DBF),
2. dBase (*.DBF),
3. Clipper (*.DBF),
4. Visual FoxPro (*.DBC),
5. Paradox (*.DB),
6. Access (*.MDB),
7. MySQL (*.MYD),
8. Interbase (*.GDB),
9. Firebird (*.FDB),
10. Excel (*.XLS),
11. CSV Text (*.CSV),
12. TAB Text (*.TAB),
13. Microsoft & Borland XML (*.XML),
14. Borland Client DataSet (*.CDS),
15. Borland DB Engine Aliases (*.BDE),
16. ADO Universal Data Link (*.UDL),
17. ODBC Data Source Name (*.DSN).
Total: 15 file types.

Main features:
* 12 file extensions: .dbf (VFP/FoxPro/dBase/Clipper), .dbc (Visual FoxPro), .db (Paradox), .mdb (Access), .myd (MySQL), .gdb (Interbase), .fdb (Firebird), .xls (Excel), .csv (Text), .tab (Text), .xml (Microsoft & Borland XML), .cds (Borland Client DataSet).
* 3 additional: .udl (ADO Universal Data Link), .dsn (ODBC Data Source Name), .bde (Borland DB Engine Aliases).
* 5 DB technologies: ADO, ODBC, Borland Engine, MySQLDAC, xBase DBF Engine. MySQLDAC is Direct Access Components for MySQL by microOLAP Technologies LLC. Tested on Oracle, DB2, SQL Server, Teradata.
* 4 methods for data searching-filtering, including incremental and quick index search.
* 7 formats for export data: dbf, xls, csv, tab, xml(Microsoft & Borland XML), html.
* 6 formats for import data: dbf, csv, tab, xml(Microsoft & Borland XML), html.
* xBase Engine automatically opens all types of index (cdx, idx, mdx, ndx, ntx) and memo (fpt, dbt) files and correctly processes their; recognizes code pages and national symbols in DBF; supports differents collates for VFP/FoxPro and autoincremental field VFP8.
* You can ñreate/modify indexes and structures of DBF/DB files and reindex, pack or zap them.
* Also you can execute SQL-Select and SQL-DDL operators for any database.

Site:
http://www.totalcmd.net/plugring/xBaseView.html

Download (1,2MB) :
http://wincmd.ru/files/wlx_xBaseView_6.1.0.563.zip

[B@rndH]

Nice and stable.

Sadly, the XML-import doesn't work (Lister selects another viewer, probably because xBaseViewer doesn't recognize the file as XML?).

Whats the criterion that a file is detected as XML-format, anyway?? My files start with

Code: Select all

<?xml version='1.0' ?>

or

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

or

Code: Select all

<?xml version="1.0" standalone="yes" encoding="UTF-8"?>

Neither was accepted by the xml-viewer (which is listed first in the wlx-plugin-list BTW).

Some hint or other would be appreciated!

Anyway, thanks for your work!

[SanskritFritz]

2B@rndH
Two things caught my eyes in the readme:
1. Microsoft & Borland XML (whatever that means)
2. Requirements
- For all databases, except DBF, DB, BDE, Borland XML and CDS, firstly are requires Microsoft ADO.
I strongly believe, that you require ADO (installed in XP by default) in order to be able to see some special xml's.

[B@rndH]

2SanskritFritz

1. Microsoft & Borland XML (whatever that means)

Apparently the components offered by MS and Bo. do produce slightly different XML code so that a universal reader will have to be rather robust to read/understand/interpret both types. AFAIK for the first viewer it was mentioned that it was a reader for the MS type, so now this is large improvement.
However, I do not know in which way the types differ, i.e. how I could possibly find out which kind of XML-file I have.

2. Requirements
- For all databases, except DBF, DB, BDE, Borland XML and CDS, firstly are requires Microsoft ADO.Well, hmm,
I strongly believe, that you require ADO (instsalled in XP by default) in order to be able to see some special xml's.

Since my question concerned XML and moreover I do use XP this should be of no concern.

BUT: dear Fritz, your approach of reading the documentation inspired me to that likewise. And I found out that there is a file "xBaseView.ext" which holds those file types resp. extensions which are ignored(!) by the viewer. I was dumbfounded to find .XML, .MDB, and .XLS listed there. Well to make a long story short: I removed the XML-entry but my files are still not read.

Regards,
B.

[SanskritFritz]

I gave the viewer a shot, and opened a Borland xml without problem. The header looks like this:
<?xml version="1.0" standalone="yes"?> <DATAPACKET Version="2.0"><METADATA><FIELDS><FIELD attrname="NAME" fieldtype="string" WIDTH="10"/><FIELD attrname="SIZE" fieldtype="i2"/><FIELD attrname="WEIGHT" fieldtype="i2"/><FIELD attrname="AREA" fieldtype="string" WIDTH="20"/><FIELD attrname="BMP" fieldtype="bin.hex" SUBTYPE="TypedBinary" WIDTH="1"/></FIELDS>
It looks very much like a database description, i would say, that this is no general xml at all, in the contrary, it is a database export.

For Microsoft, i couldnt find an xml openable by the plugin.

[B@rndH]

2SanskritFritz
I'd like to give that file of yours a shot; if it doesn't work for me it is a configuration error on my side (although everything else works) and if it works my files are the problem and I will have to look for another way to have a look into them.

[SanskritFritz]

2B@rndH
So I uploaded the file here:
http://rapidshare.de/files/7940154/animals.xml.html

[B@rndH]

2SanskritFritz
Thanx a lot. Worked like a charm on the first try.
I'm dumbfounded since I haven't yet a clue why my files don't work.
But since I now know that it does work I'll keep trying! Thanks again!

[SanskritFritz]

2B@rndH
As I said, the plugin is a database viewer, so i would expect only database exports to work.
xml in general can hold data in a tree view, no grid is able to represent this data.

[B@rndH]

2SanskritFritz
Had a tighter look at my file: it is a more tree-like structure although the author declares it to be a database! That explains it probably. Thanks for your patience & interest.

[JohnFredC]

Thanks for this plugin!

The F10 context menu mentioned in the ReadMe doesn't work in TC QuickView on my system. How do I access the export function from QuickView?

On my system, no context menu appears for databases, tables, or data in QuickView.

Also, where is the INI created and what is it called?

TC 6.53

Thanks again!

[mutex]

2SanskritFritz
Many thanks for You explanations!

2JohnFredC
This is made so for program stability.

Author.

[Juergen]

Thanks for this great plugin!

Just some notes concerning the file "xBaseDeutsch.lng":

Code: Select all

- Line   : xSDrivesCap=Treiber:
  must be: xSDrivesCap=Laufwerke:
  
- Line   : Caption=Verzeichniswahl - [Enter] oderr Doppelclick
  must be: Caption=Verzeichniswahl - [Enter] oder Doppelklick

- Line   : Caption.mnuReindex=Reindizeirung   
  must be: Caption.mnuReindex=Reindizierung 

Also, on my System ( Windows 98 ) depending on the context the German Umlauts are sometimes displayed correctly, but sometimes not. For instance, in the "File" menu there is the correct entry "Öffnen" ("Open" in English), but in the button bar there is an entry "Lµschen" ("Delete" in English), which must correctly read "Löschen".

Regards, Jürgen

[Clo]

2Juergen
Hello !
• Same here in French about accented characters, though I run XP-Pro…

• I've reported this to mutex via email (because other issues, tedious to read here…). According to his answer, he might try to fix up that.

- I guess this is caused by the internal hard-coded font. Depending on whether he'll change to a complete named font - i.e. : either Arial Latin or Tahoma Latin, or rather a generic font like MS Shell Dlg (the default font of Windows 2K¦XP), you will get the correct characters, or not.
- Under Win 98SE, you can add in your file <…\Windows\WIN.INI> :
[FontSubstitutes]
MS Shell Dlg=Arial
Microsoft Sans Serif=Arial
- The second line in the case of that font should be chosen (or is set) -it doesn't exist under Win9x and you can't add it-.
- Now, just wait and see…

 V.G.
Claude
Clo

[Juergen]

Hi Clo,

thanks for your comprehensive reply!

I've reported this to mutex via email (because other issues, tedious to read here…). According to his answer, he might try to fix up that.

That would be nice.

Concerning the WIN.INI file, on my system it was:

Code: Select all

[FontSubstitutes]
MS Shell Dlg=MS Sans Serif

According to your post, I changed the line, and added the other line, so that it now reads:

Code: Select all

[FontSubstitutes]
MS Shell Dlg=Arial
Microsoft Sans Serif=Arial

After rebooting the system, there are still the same problems as before. Well, I think for now I'll use xBaseView's English language interface, rather than the German one. But there are a lot of people in Germany who don't speak English ...

Thanks again,
Juergen