Replies

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

looking into this, thought i’d swing by the lounge…

in SQL Server, you often do things like If Exists

Drop Table as a standard check prior to trying to create the object. In Access, I have tabledef code in place and I want to do the same check to make sure I never try to create a table def if the linked table already exits.

So, looking for the syntax…

TIA!

Yes, it’s clear now what you meant. I gather that I would use header() to perform the actual load of the new page.

This is a useful technique, and I thank you for it. If I had had it when I started this thread, though, I probably would still have chosen the kludge I used. The problem is that sessions, as I understand it, require the use of cookies, and this site site was designed to work without cookies. The client understands that virtually all web commerce sites use cookies these days, but nevertheless believes that they would pose technical problems and/or drive away some potential customers. Researching and evaluating that issue is way beyond what I’ve been asked to do, and it wouldn’t make sense for a site that is just being patched up to work until it can be replaced.

I’m still puzzled that this apparently simple requirement has opened such a can of worms, but I’m ready to move on.

At this point I’m much more concerned about the problem in the other thread I started, concerning magic quotes. If you could take a look at that one and make suggestions, I’d be grateful.

can you not send the submitted data to a processing page that takes the data and, using a simple Select Case routine, transfers the user to Form A or B, depending? I do this all the time. the user doesn’t know they passed thru the processing page; you can preserve form field across multiple pages several ways without resorting to cookies. I don’t know what technology you are using, so there’s some differences in syntax depending.

thanks – tried it out. seems to work!

Well, what i have is an unbound Textbox on the report with the control source set to =”Printed on: ” & Now(), which reflect the time the report was opened. what i was looking for is some event called ‘OnPrint’. if it doesn’t exist, fair enough, just will have to advise the time stamp is the time the report is opened, not printed.

Also see Allen Browne – Creating an Audit Log.

interesting article on audit logging. not sure if i’ll use it but nice to know about the option.

Thanks – I’ll think about doing the time stamp column. what i want is a quick way to automatically flag all rows where some changes was made.

Can you clarify what the problem was here?
Was it that you wanted some controls to have both “UE” and “OR” in their Tag, so they belonged to both groups?
In that case, yes you would need to use:

Code:

If (InStr(1, .Tag, "OR") > 0) Then

rather than

Code:

If .Tag = "OR" Then

I often use code like this (looping through controls checking for something in their Tag property), so I am just wondering if there is some pitfall here I was not aware of.

I have a set of controls that are “OR” and another set that are “UE”. there’s no overlap. some other controls have no tag at all, and the first code block (which polls based on Tag info) does, correctly, ignore controls with no tag data. it’s just that if i try to poll UE controls using the Tag technique it mysteriously fails. since i have prepends on those controls, i can still pick them up in a loop but it’s a weird thing to have to do…

Problem mostly solved. I dynamically link the SQL Server table in and run UPDATE with the Access query providing the set of records to update. Much like Francois’s code. The issue was trying to combine data from SQL Server and Access in one command.

Are you sure about the query names ?
In your first post you mention qryOrigRUGItems and now qryEditRUGitems

yes I’m sure. the correct query is the edit one. What i think i need to do is, dynamically link the table in question into Access rather than do something fancy like run UPDATE directly out of Access into SQL Server.