could use javascript (ajax) to send the form variables to the remote site on submit

nice to see someone helping just because they can
:)
hugs to you

Is this thread like a Mexican house painter offering to paint your fully customized 57 chevy? FOR FREE?

...it gets wet and you find that the seats were stuffed with horse shit?

Yeah, this is the one.

Now now, settle down.

If what you want to use php to get a variable with the country code, you will end up having to use php to get a variable loaded with the country code. There'd obviously be better ways to solve this problem, but this is what was originally requested, a simple way to solve it, that can be dropped into various projects w/o hassle.

Incidentally, if you want to filter or redirect hits you're better off putting ip lists in your hosts or htaccess than using php to begin with.

Why are you so aggro anyway ?

This depends on what exactly you're trying to accomplish and how.

Off the top of my head, INSERT allows for ON DUPLICATE KEY UPDATE, which can also use a compound (unique) key to check for duplication. This is very userful. For example:
If you have a log table to log hits to different websites daily, with "site_id"-s and "time" fields, where neither of them are primary keys, but togethether they are unique, then you can create a key on them, and then use "...ON DUPLICATE KEY..."

There's also the issue of permissions, where UPDATE only requires UPDATE priviledges whereas INSERT requires both INSERT and UPDATE, which might or might not be an issue.

I'm sure there's more.

Well, suppose you have http://domain1.com/form1.php and http://domain2.com/form2.php as your two forms.

Now, on form1.php, make sure you include

<FORM action="http://domain2.com/form2.php" method="post">

In form2.php, make sure you include

<input type="checkbox" name="item_name" value="<?php echo $_POST["item_name"]; ?>">

Make sure you use the same item_name in both forms, and make sure you do this for every input element on the 2nd forum.

Cheers.

Hugs right back hehe

ok thanks i will give it a try and let everyone know how it works

whats the going rate for coders these days anyway?

:) :) :)

Your system does more harm than good. That's why I called you out on it; sometimes it's better not to have something than to have something detrimental. Much like a homebrew blog that does a 'SELECT * FROM `table`', this system is beyond suboptimal - it shows you have put no thought into the actual design, even if it's an amazingly trivial thing - if it's called once per page hit, that's outright dangerous.

Even when it FINDS one, it doesn't break; it keeps on going straight through, so, hey, yeah, I see you, but I'm still calling the next 1,000 to see if maybe you fit those, too.

So, you don't know the easiest way to compute the ip, you're using a text lookup table, and you're gonna be killing that CPU for a few moments as well as the unnecessary overhead.

You've made a functional, but not viable solution. Don't do that.