headers
Alan Chan | 1 Nov 2009 01:50

Re: Error -1 on Convert to Text

4D iNug Technical <4d_tech@...> writes:
>Convert to text after CONVERT FROM TEXT is safe.

This is what generate error -1. CONVERT FROM TEXT-> Convert to text
>
>BLOB to text after TEXT TO BLOB is safe.

TEXT TO BLOB seems correctly convert utf-16 back to Mac text but Blob to
text doesn't support Big5.
>
>2004->v11 conversion is similar to the latter convention,
>so you should use TEXT TO BLOB not CONVERT FROM TEXT.

TEXT TO BLOB does convert back to macroman, but Convert to text would
generate error -1 in "some" cases.

After all these tests, it seems to me that Convert to text is the one that
chokes.

Alan Chan

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Livingston | 1 Nov 2009 08:14
Picon

Japanese Characters as ???

I have a database table into which I have imported two fields from a  
text file.

One of these two fields contains Japanese characters.

The text file itself looks like

A01.0.00.001	垂直
A01.0.00.002	水平
A01.0.00.003	正中
A01.0.00.004	冠状
A01.0.00.005	矢状
A01.0.00.006	右
A01.0.00.007	左

When I import it looks like the below in an output layout

A01.0.00.001	??
A01.0.00.002	??
A01.0.00.003	??
A01.0.00.004	??
A01.0.00.005	??
A01.0.00.006	?
A01.0.00.007	?

If I go to an individual input layout it looks like

Field 1        A01.0.00.005	
Field2         ??
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Livingston | 1 Nov 2009 08:49
Picon

Japanese Characters as ???

This problem has mysteriously gone away. I upgraded to V11.4 (from  
V11.1) and reopened the database and the problem not there.

I do not know whether it was the upgrade or what but the problem  
disappeared.
**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************
Permalink | Reply | 0 comments |
headers
Basil Bourque | 1 Nov 2009 09:23
Picon

Re: Mac Mini Server

Some folks may be missing the point of the Mac mini server's software  
and hardware.

----|  Software  |---------

The Mac mini server comes with "Snow Leopard Server", while the other  
Mac minis come with "Snow Leopard". Both are the same OS, Mac OS X,  
with the same code base.
http://www.apple.com/server/macosx/

The difference is that the server version of Mac OS X adds a slew of  
server-oriented programs such as file server, email server, web  
server, Java servlet server, calendar server, instant message server,  
Spotlight search server, Authentication servers, and much more. Many  
of these are open-source projects you could download and install on  
Mac OS X (non-Server). But Apple has saved you the time and trouble  
with Mac OS X Server.
http://www.apple.com/server/macosx/features/

Apple also built some software to wrap many of those programs for  
simplified administration.
http://www.apple.com/server/macosx/features/simple-administration.html

None of this will make your 4D Server run faster!!!
Just the opposite: More software competing for CPU and memory.

If you want a server to run only 4D Server, there is no need to buy  
Mac OS X Server.

Unlike certain other large vendors, Apple does not charge a fee for
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nigel Greenlee | 1 Nov 2009 09:58

Re: Converting subtables in v11

All
I concur with this having dealt with the users of a commercial  
application for the past nearly 10 years, if i have learned a couple  
of things on upgrades it is this.

1) Don't over estimate the technical abilities of your users

2) Don't under estimate the ability of the users to take a process you  
think you have kept simple and break it. (or find the flaws!)

and specifically on the upgrade to V11 i have taken this approach:-

I have an application that contains about 10 subtables in 4D 2004 with  
about 6000 references to those subtables in the code and to get SQL  
compliant an important step is to get rid of the subtables, many  
clients over the years have wanted to use ODBC/SQL tools with our  
product which has never been practical, and reporting on the subtable  
information has always been a nightmare(several of the subtables  
should never have been subtables).

1) In our 2004 product I produced a final version. This is better for  
the users than an interim version which I did This version has code in  
to export the data. The code uses, EXPORT RECORD on all tables where  
there is no subtable-this is fast and tried and tested as a data  
transfer solution. On tables with a SUBTABLE we export the data from  
the main table into variables using a field name and data pairing,  
missing out the subtable field and data.. Then we export into a  
seperate document the subtable information in the same fashion but ADD  
the parent record KEY Field. Remodelling our existing export all data  
routine to do this really only took a few hours(and then several more
(Continue reading)

Permalink | Reply | 2 comments |
headers
psmith | 1 Nov 2009 10:33

Re: Converting subtables in v11

Nigel,

I know you've already finished the job, but what would you think about  
this approach.

1) Create a final version of your 2004 database with new tables to  
replace all subtables with tables and eliminate all references to  
subtables in your code.

2) This final version could then usse EXPORT RECORD on all the tables,  
not just the ones without subtables.

3) Import the data in v11 with IMPORT RECORD into a fresh structure  
with no references at all to subtables (by dropping the subtable ID  
field etc)

This is similar to your approach, but avoids having to export the  
subtable records in text files. You do, of course, have to write code  
to populate the new tables in the 2004 database.

I'm not sure which version would be faster. I guess it would depend on  
the number of subtables you're dealing with.

Paul Smith

TSE International

> All
> I concur with this having dealt with the users of a commercial  
> application for the past nearly 10 years, if i have learned a couple
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bill Michling | 1 Nov 2009 15:21
Favicon

Re: Mac Mini Server

The main reason I recommend the xServer, as it does have redundant  
power supplies, live slide in out hard drives, and such...

Cool...
-----------------
Bill Michling
bill@...
-----------------

On Nov 1, 2009, at 2:23 AM, Basil Bourque wrote:

> What you don't get, as in a "real server", is redundant higher- 
> quality power supplies, redundant fans, higher-performance and  
> higher-reliability hard drives, hardware-based RAID, and lights-out  
> management.

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************
Permalink | Reply | 0 comments |
headers
Douglas von Roeder | 1 Nov 2009 18:28
Picon

Tools doesn't create new Database

This has happened a few times to me over that past year, all with the same
structure.

When I open the structure file in Tools and run Compact, Tools creates a
file for the new db and the .RSR but it then very quickly deletes the .4DB
file. In contrast, when I "Repair" the db, the .4DB and .RSR files are
created.

This is a 2004.7r3 db whose that runs on Windows and I'm using 4D Tools
2004.7r3.

Any insights into this?

--
Douglas von Roeder
**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************
Permalink | Reply | 0 comments |
headers
Michael Ashton | 1 Nov 2009 20:23
Picon

4D Write freeze references

I have not used 4D Write in a long time. I have to convert a database from
V6.5 to 2004/V11.

How do you [programmatically] freeze references *ONLY* in the header. In the
days of 6.5 you would execute the command to show header, select all the
text, then execute the command to freeze references. This would freeze only
references in the selected text of the header. I guess the show header and
show footer commands work differently now. Any help appreciated.

Michael Ashton
**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************
Permalink | Reply | 2 comments |
headers
Nigel Greenlee | 1 Nov 2009 23:02

Re: Converting subtables in v11

Paul

I did try that in a test with one subtable. The new table exactly  
matched my table in V11 but still the 'IMPORT RECORD' caused a crash  
when it tried to import the data so i gave up on it. Although  
exporting the data out using variables is slower it works and is it a  
one time operation was not worth investing a whole heap of time into  
investigating why.

One thing i have been considering though which i would do if I
1) Had time
2) was doing this again

Would be to have the import able to to a second import without  
recreating everything...Why? Because the export import is a tedious  
task and if a user could set aside the datafile after the import they  
could all their testing and then import just updates from their live  
system to the ready to go datafile and save a lot of time..but I guess  
if i was going that far i would probably just a 4D-4D connection 
(SOAP)...

On 1 Nov 2009, at 09:33, psmith wrote:

> Nigel,
>
> I know you've already finished the job, but what would you think  
> about this approach.
>
> 1) Create a final version of your 2004 database with new tables to  
> replace all subtables with tables and eliminate all references to
(Continue reading)

Permalink | Reply | 0 comments |

Gmane