Replies

I believe that it has to do with the Size, Precicision, and Scale of the data fields.

In one of my Access 97 apps SQL numeric fields with 5(5,0) are shown as Number, Long Integers in Access.
Numeric fields with 13(22,6) and 13(20,0) are shown as Text in Access.

I can think of three ways to solve the problem:
(1) Modify the SQL tables to a lesser scale and precision
(2) Use the conversion functions (CDbl, CInt, CLng, etc.) to change the data type in queries, reports, etc.
(3) Updgrade to Access 2000, which doesn’t seem to have this problem.

Novell is long gone.
It has to be a Microsoft solution.

I used the following books when setting up a web based Access database.

Beginning ASP Databases by John Kauffman (ISBN: 1-861002-72-6)

Teach Yourself Active Server Pages 3.0 in 21 Days by Scott Mitchell and James Atkinson (ISBN: 0-672-31863-6)

FrontPage 2000 Developer’s Guide by Mike Jennett (ISBN: 0-07-211972-1)

I link to the SQL tables using the ODBC connection.

Once the tables are linked, I create queries and reports as you normally would in Access.

My clients are only interested in reporting information that is stored in SQL, so this solution works fine.

Thanks for the link.

What ‘registry patch’ were you referring to?

Can you post a link to the site?

Thanks.

The help is working now.

Thanks.

If you are checking a Date field, I believe that you have to enclose your the date in the number sign, #.

If Not IsNull(DLookup(“dteSumDate”, “tblSumServe”, “dteSumDate= #” & Me!BatchDate & “#”)) Then

Thanks.

Since this situation will not occur on a regular basis, I went with creating two connections.

It worked perfectly.

Changing the Allow Zero Length Strings setting to True seems to have corrected my updating problems.

Thanks,

I ‘think’ that I’ve narrowed the problem down to Null values on the input form.

Although many of the database fields are not required, if I leave some of them blank on the form, the record isn’t updated. However, if I enter something into each field, I can update the record.

Does this make sense?

The current design of the database does not allow Zero Length Strings. Should I change this field setting?

The script worked.

However, I had to remove all of the ‘comments’ relating to the FrontPage bots that were generated by FrontPage validation.

It appears that FrontPage generates the Javascript validation script on the fly, thereby erasing the code I entered.

I use VBScript with ASP to block private pages from public viewing.

When a member logins in, the following session variable is set as part of the login routine.
Session(“vIDOK”)=True

I put the following code at the top of each private page:

Anyone not logged in that attempts to load the page is re-directed to the login page.

Does Javascript have a limit to the number of nested IFs? (I think Excel has a limit of 7.)

Besides validating each input as the user enters data, I want the submit button to perform a final validation before submitting the form.

I saw an example in a Javascript book for testing 3 input fields. Adapting the example to my form with fourteen input fields would generate code similar to the following:

function CheckAll(form)
{
if (IsAlpha(form.FirstName,True)){
(IsAlpha(form.MiddleInitial,False)){
(IsAlpha(form.LastName,True)){
(IsEmailValid(form.EmailAddress,False)){
(IsYear(form.JoinedYear)){
(IsAlpha(form.WorkCity,False)){
(IsState(form.WorkState,False)){
(IsZip(form.WorkPostalCode,False)){
(IsPhone(form.WorkPhone,False)){
(IsPhone(form.WorkFaxNumber,False)){
(IsAlpha(form.HomeCity,False)){
(IsState(form.HomeState,False)){
(IsZip(form.HomePostalCode,False)){
(IsPhone(form.HomePhone,False)){
return true;
}
}
}
}
}
}
}
}
}
}
}
}
}
}
return false;
}

NOTE: the True or False indicates to the validating function whether the field is required.

Is there any easier way to accomplish this?

The attachment has some of the actual validation routines.

(Edited by Leif to make link live – see the quick guide)

I’ve used Snitz Forum – http://forum.snitz.com[/url%5D.

This is an MS Access/ASP solution.

It’s been running since last October without a problem and works a lot better than using a FrontPage discussion web.

If you want to see a live example, go to:
http://www.mountainnature.com/forum/default.asp%5B/url%5D